Tap interface select circuit with AUX1/02-TMS and TMS/RCK-RCK leads

ABSTRACT

This disclosure describes a reduced pin bus that can be used on integrated circuits or embedded cores within integrated circuits. The bus may be used for serial access to circuits where the availability of pins on ICs or terminals on cores is limited. The bus may be used for a variety of serial communication operations such as, but not limited to, serial communication related test, emulation, debug, and/or trace operations of an IC or core design. Other aspects of the disclosure include the use of reduced pin buses for emulation, debug, and trace operations and for functional operations. In a fifth aspect of the present disclosure, an interface select circuit, FIGS.  41 - 49 , provides for selectively using either the 5 signal interface of FIG.  41  or the 3 signal interface of FIG.  8.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a divisional of prior application Ser. No.13/102,742, filed May 6, 2011, now U.S. Pat. No. 8,145,962, issued Mar.27, 2012;

Which was a divisional of prior application Ser. No. 12/985,876, filedJan. 6, 2011, now U.S. Pat. No. 7,962,818, issued Jun. 14, 2011; Whichwas a divisional of prior application Ser. No. 12/840,928, filed Jul.21, 2010, now U.S. Pat. No. 7,890,829, issued Feb. 15, 2011; Which was adivisional of prior application Ser. No. 12/563,775, filed Sep. 21,2009, now U.S. Pat. No. 7,793,182, issued Sep. 7, 2010; Which was adivisional of prior application Ser. No. 11/954,403, filed Dec. 12,2007, now U.S. Pat. No. 7,613,970, issued Nov. 3, 2009; Which was adivisional of prior application Ser. No. 11/293,061, filed Dec. 2, 2005,now U.S. Pat. No. 7,328,387, issued Feb. 5, 2008. Which claims priorityfrom Provisional Application No. 60/634,842, filed Dec. 10, 2004.

This application is related to U.S. patent application Ser. No.10/983,256, filed Nov. 4, 2004, titled “Removable and Replaceable TapDomain Selection Circuitry,” and U.S. patent application Ser. No.11/258,315, filed Oct. 25, 2005, titled “2 Pin Bus.”

BACKGROUND OF THE DISCLOSURE

This disclosure relates in general to IC or core signal interfaces andparticularly to IC or core signal interfaces related to test, emulation,debug, trace, and function operations.

DESCRIPTION OF THE RELATED ART

FIG. 1 illustrates an IC or embedded core circuit 100 containingfunctional circuits 102, IEEE 1149.1 (JTAG) circuit 104, and emulation,debug, and/or trace circuit 106. The functional circuit 102 communicatesexternally of the IC or core via bus terminals 103. The 1149.1 circuitcommunicates externally of the IC or core via bus terminals 108 andinternally to the functional circuit 102 via bus 114. The emulation,debug, and/or trace circuit communicates externally of the IC or corevia bus terminals 110 and internally to the functional circuit 102 viabus 112. As seen, the 1149.1 circuit 104 comprises data registers 116,instruction register 118, mux 122, falling clock edge FF 124, tristatebuffer 128, and test access port (TAP) controller 120. The 1149.1circuit 104 has external terminals on bus 108 for a test data input(TDI) 132, a test mode select (TMS) 134, a test clock (TCK) 136, a testreset (TRST) 138, and test data output (TDO) 140 signals. The dataregisters 116 comprise a set of serially accessible registers, someproviding input and output to functional circuit 102 via bus 114. Theregisters can be used for performing boundary scan test operations onfunctional bus terminals 103, performing internal scan testing of thefunctional circuit 102, and/or supporting debug, trace, and/or emulationoperations on the functional circuit 102. As indicated, a power up clear(PUC) circuit 130, which is a circuit for resetting or initializing agiven circuit upon application of power, may be used instead of or incombination with the TRST terminal to set the state of the Tap 120 inthe 1149.1 circuit 104.

FIG. 2 illustrates an IC 200 containing four JTAG circuits 104. One JTAGcircuit 104 is associated with non-core circuitry in the chip and isreferred to as the Chip Tap Domain 202. The other JTAG circuits 104 areeach associated with circuitry of an embedded core and are referred toas Core Tap Domains 204-208. The Tap domains 202-208 are shown in Tapdomain region 201. The JTAG circuit 104 bus terminals 108 of each Tapdomain 202-208 may be coupled to chip terminals 212-220 via a Tap DomainSelection circuit 210. Once coupled, the JTAG circuit 104 of a selectedTap domain 202-208 may be accessed via chip terminals 212-220 for test,debug, trace, and/or emulation operations by an external controller. Avariety of Tap domain selection circuits 210 that could be used in thisexample are described in a referenced paper entitled “An IEEE 1149.1Based Test Access Architecture for ICs with Embedded Cores” authored byWhetsel and presented at the IEEE International Test Conference inNovember of 1997.

When using a Tap Domain Selection circuit as shown in FIG. 2 it is bestto remove the TDO tristate buffer 128 of JTAG circuits 104, if possible,to allow the flip flop 124 of the JTAG circuit 104 to directly drive theTDO signal on the interface 108 between the JTAG circuit 104 and the TapDomain Selection circuit. This practice prevents floating (i.e.tristate) TDO signal lines inside the IC/core.

FIG. 3 illustrates an IC or embedded core circuit 300 containingfunctional circuits 102, JTAG circuit 302, and emulation, debug, and/ortrace circuit 106. The IC 300 is identical to IC 100 of FIG. 1 with theexception that JTAG circuit 302 is different from JTAG circuit 104. Thedifference is that the JTAG circuit 302 includes a flip flop (FF) in theTCK path to the Tap 120. The D input of the FF is coupled to the TCKsignal 136, the Q output of the FF is coupled to the TCK input of theTap 120, and the clock input of the FF is coupled to a functional clock(FCK) output 306 from function circuit 102. The Q output of the FF isalso output as a return clock (RCK) output on terminal 308 of bus 310.The difference between bus 108 of FIG. 1 and bus 310 of FIG. 3 is theadditional RCK signal 308. The use of FF 304 in JTAG circuit 302 forcesthe TCK signal from an external controller to be sampled by the FCK 306before it is allowed to be input to the Tap 120. The RCK output 308 tothe external controller indicates to the external controller when theTCK signal has been sampled by the FCK. For example, if the externalcontroller sets TCK 136 high, the RCK signal 308 output will go highwhen the FCK 306 clocks the TCK into FF 304. When the controller sees ahigh on RCK, it can set TCK low and again wait for the RCK to indicatewhen the low on TCK has been clocked into the FF 304 by the FCK 306.This method of operating the JTAG circuit 302 allows the externalcontroller to synchronize the operation of the TCK signal to thefrequency of the FCK signal, using the handshaking operation provided bythe RCK signal. This TCK handshaking technique, while not compliant tothe IEEE 1149.1 standard, is being designed into embeddable coresprovided by ARM Ltd. Thus the technique must be adopted in ICs that useembedded cores from ARM Ltd.

FIG. 4 illustrates an IC 400 containing four JTAG circuits 302. One JTAGcircuit 302 is associated with non-core circuitry in the chip and isreferred to as the Chip Tap Domain 402. The other JTAG circuits 302 areeach associated with circuitry of an embedded core and are referred toas Core Tap Domains 404-408. The Tap domains 402-408 are shown in Tapdomain region 401. The JTAG circuit 302 bus terminals 310 of each Tapdomain 402-408 may be coupled to chip terminals 412-422 via a Tap DomainSelection circuit 410. Once coupled, the JTAG circuit 302 of a selectedTap domain 402-408 may be accessed via chip terminals 412-422 for test,debug, trace, and/or emulation operations by an external controller. TheTap domain selection circuit 410 is similar to the Tap domain selectioncircuit 210 of FIG. 2 with the exception that it includes additionalcircuitry for coupling the RCK 308 output of a selected Tap domain402-408 to the RCK chip terminal 422.

SUMMARY OF THE DISCLOSURE

In a first aspect of the present disclosure, a method and apparatus isdescribed in FIGS. 5-30 for addressing, instructing, and accessing TapDomains in ICs or core circuits using a reduced number of signalterminals. In a second aspect of the present disclosure, a method andapparatus is described in FIGS. 31-34 for accessing a target Tap domainin an IC or core circuit using a reduced number of signal terminals. Ina third aspect of the present disclosure, a method and apparatus isdescribed in FIGS. 35-36 for reducing the number of IC or core signalterminals involved with emulation, debug, and trace operations. In afourth aspect of the present disclosure, a method and apparatus isdescribed in FIGS. 37-40 for reducing the number of IC or core signalterminals involved in function I/O operations. In a fifth aspect of thepresent disclosure, a method and apparatus is described in FIGS. 41-49for selectively using either the 5 signal interface of FIG. 41 or the 3signal interface of FIG. 8.

DESCRIPTION OF THE VIEWS OF THE DRAWINGS

FIG. 1 illustrates an IC or core with a standard JTAG circuit TapDomain.

FIG. 2 illustrates an IC or core having plural standard JTAG circuit TapDomains and Tap Domain selection circuitry.

FIG. 3 illustrates an IC or core with a non-standard JTAG circuit TapDomain.

FIG. 4 illustrates an IC or core having plural non-standard JTAG circuitTap Domains and Tap Domain selection circuitry.

FIG. 5 illustrates an IC or core including the addressable Tap DomainSelection circuit of the present disclosure.

FIG. 6 illustrates more detail view of the addressable Tap DomainSelection circuit of the present disclosure.

FIG. 7A illustrates the operation of the Tap Domain Selection Circuit ofthe present disclosure in response to first, second, and thirdprotocols.

FIG. 7B illustrates sequences of first, second, and third protocols ofthe present disclosure.

FIG. 8 illustrates a detail view of the Addressable Tap Domain SelectionCircuit interfaced to plural Tap Domains.

FIG. 9 illustrates a detail view of the Address circuit of the presentdisclosure.

FIG. 10 illustrates a detail view of the Instruction circuit of thepresent disclosure.

FIG. 11 illustrates a detail view of the Tap Linking circuit of thepresent disclosure.

FIG. 12 illustrates the Reset, Address, and Instruction Controllers ofthe present disclosure.

FIG. 13 illustrates a detail view of the Hard and Soft reset controllersand sequences of the present disclosure.

FIG. 14 illustrates the state diagram of the Address and Instructioncontroller of the present disclosure.

FIGS. 15A and 15B illustrate detail views of the Address and Instructioncontroller of the present disclosure.

FIG. 16 illustrates the state diagram of the standard IEEE 1149.1 Tapcontroller.

FIG. 17 illustrates the connection between an external controller andthe circuitry of the present disclosure existing in ICs or corecircuits.

FIG. 17A illustrates the connection between an external controller andthe circuitry of the present disclosure existing in stacked diecircuits.

FIG. 18 illustrates the connection between an external controller and acircuit containing the present disclosure that is interfaced to standardlegacy JTAG circuits in ICs or cores.

FIG. 19 illustrates the connection between an external controller and acircuit containing the present disclosure that is interfaced to standardlegacy JTAG circuits in ICs or cores, and to ICs or cores that includethe circuitry of the present disclosure.

FIG. 20 illustrates the TDI/TDO connection between I/O buffers of thepresent disclosure existing in an external controller and in target ICsor cores.

FIG. 21 illustrates the TMS/RCK connection between I/O buffers of thepresent disclosure existing in an external controller and in target ICsor cores.

FIG. 22 illustrates the data input circuit of I/O buffers of the presentdisclosure.

FIG. 23A-23D illustrates the operation of the output buffer of the I/Ocircuits of the present disclosure existing in an external controllerand a target IC or core.

FIG. 24 illustrates the four cases of signal flow between the I/O bufferof an external controller and the I/O buffer of a target IC or core.

FIGS. 25-28 illustrate different sequences of performing first andsecond protocols of the present disclosure.

FIG. 29 illustrates the sequence of performing a second protocol, then athird protocol, then a first protocol according to the presentdisclosure.

FIG. 30 illustrates the sequence of performing a second protocol, then afirst protocol according to the present disclosure.

FIG. 31 illustrates an interface between an external controller and astandard JTAG circuit within an IC or core.

FIG. 32 illustrates a reduced interface between an external controllerand a standard JTAG circuit within an IC or core according to thepresent disclosure.

FIG. 33 illustrates an interface between an external controller and anon-standard JTAG circuit within an IC or core.

FIG. 34 illustrates a reduced interface between an external controllerand a non-standard JTAG circuit within an IC or core according to thepresent disclosure.

FIG. 35 illustrates an interface between an external controller andemulation, debug, and trace circuits within an IC or core.

FIG. 36 illustrates a reduced interface between an external controllerand emulation, debug, and trace circuits within an IC or core accordingto the present disclosure.

FIG. 37 illustrates a functional interface between first and secondfunctional circuits of an IC or core.

FIG. 38 illustrates a reduced functional interface between first andsecond functional circuits of an IC or core according to the presentdisclosure.

FIG. 39 illustrates a functional interface between a master functionalcircuit in a first IC or core and slave functional circuits in secondand third ICs or cores.

FIG. 40 illustrates a reduced functional interface between a masterfunctional circuit in a first IC or core and slave functional circuitsin second and third ICs or cores according to the present disclosure.

FIG. 41 illustrates an Addressable Tap Domain Selection circuit similarto that of FIG. 8 with the TDI, TDO, TMS, and RCK signals coupled viabuffers to externally accessible signal terminals.

FIG. 42 illustrates a group of target devices on a board or othersubstrate, each target device including the Addressable Tap DomainSelection Circuit and its associated 5 pin TCK, TDI, TDO, TMS, and RCKinterface, as well as Tap Domain Region.

FIG. 43 illustrates the legacy target devices of FIG. 18, each includingthe standard IEEE 1149.1 TRST, TCK, TMS, TDI, and TDO terminals, andoptionally the non-standard RCK terminal.

FIG. 44 illustrates an Addressable Tap Domain Selection circuit that hasbeen designed in an IC or core to selectively use either the 5 signalinterface of FIG. 41 or the 3 signal interface of FIG. 8.

FIG. 45 illustrates an example design of the Interface Select Circuit ofFIG. 44.

FIG. 46 illustrates an example of the configuration of the InterfaceSelect Circuit when it is in the 3 signal interface mode.

FIG. 47 illustrates an example of the configuration of the InterfaceSelect Circuit when it is in the 5 signal interface mode.

FIG. 48 illustrates a group of target devices on a board or othersubstrate, each target device including the Addressable Tap DomainSelection Circuit of FIG. 44 and its selectable 3 or 5 pin interface.

FIG. 49 illustrates the legacy target devices of FIG. 18, each includingthe standard IEEE 1149.1 TRST, TCK, TMS, TDI, and TDO terminals, andoptionally the non-standard RCK terminal and the Addressable Tap DomainSelection Circuit of FIG. 44 operating in either the 3 or 5 signalinterface mode.

DETAILED DESCRIPTION

FIG. 5 illustrates an IC 500 including the test, debug, trace, and/oremulation architecture of the present disclosure. The architectureincludes a Tap domain region 522 comprising individual Tap domains502-508. Each Tap domain 502-508 includes a JTAG circuit 510, which canbe either the conventional JTAG circuit 104 or the modified JTAG circuit302. Each JTAG circuit 510 is coupled to an Addressable Tap DomainSelection circuit 514 via buses 512. If a JTAG circuit 510 is aconventional JTAG circuit 104, its bus 512 will be the same as bus 104.If JTAG circuit 510 is a modified JTAG circuit 302, its bus 512 will bethe same as bus 310.

Addressable Tap domain selection circuit 514 is coupled to external ICterminal signals TCK 516, TMS/RCK 518, and TDI/TDO 520. The TCK 516signal is the same as the TCK 214 signal shown in FIGS. 2 and 4, withthe exception that, in addition to operating as a clock input to the IC500 from an external controller, the TCK 516 of FIG. 5 can also beoperated as a data input and a control input from the externalcontroller, according to a first protocol defined by the presentdisclosure. The TMS/RCK 518 signal is a signal defined by the presentdisclosure to operate as a signal that can serve as either an inputsignal to the IC 500 from an external controller or as a simultaneousinput/output between the IC 500 and the external controller. Similarly,the TDI/TDO 520 signal is a signal defined by the present disclosure tooperate as a signal that can serve as either an input signal to the ICfrom an external controller or as a simultaneous input/output betweenthe IC and the external controller.

FIG. 6 illustrates in more detail the connections between theAddressable Tap Domain Selection circuit 514 and the Tap Domains 510 inTap domain region 522. Selection Circuit 514 is coupled externally ofthe IC via signal terminals TCK 516, TMS/RCK 518, and TDI/TDO 520. Asseen, pull up elements, pull down elements, or other state holdingelements 602 such as bus holders are preferably connected to theseterminals to allow them to be set to a known state when they are notexternally driven. Selection circuit 514 is coupled to the Tap domains1-4 in Tap region 522 via TDI 1-4 signals 132, TDO 1-4 signals 140, TMS1-4 signals 134, RCK 1-4 signals 308, TCK signal 136, and TRST signal138.

In this example, the Tap region 522 is assumed to contain four Tapdomains 510 with all four Tap domains 510 being modified Tap domain 302types. Thus each of the four Tap domains 510 will have a RCK 308 output(1-4) to the Selection circuit 514. In another example, the Tap region522 may contain four Tap domains 510, each being conventional Tap domain104 types, which would eliminate the need for the RCK signal connectionsto the Selection circuit 514. In still another example, the Tap region522 may contain mixtures of modified Tap domains 302 requiring RCKsignal connections and conventional Tap domains 104 not requiring RCKsignal connections. Also while this example shows four Tap domains 510in Tap region 522, a lesser or greater number of Tap domains 510 (104 or302 types) may exist in Tap region 522.

The purpose of the Addressable Tap Domain Selection circuit 514 is toallow for an external controller coupled to terminals 516-520 to inputan address to the Selection circuit 514 of the IC then load aninstruction into the Selection circuit 514 of the IC. The loadedinstruction may provide a plurality of control functions within the IC,at least one control function being to control which one or more Tapdomains 510 in Tap region 522 is selected for access by the externalcontroller.

In applications of the present disclosure, a plurality of ICs may becoupled, at some point, to an external controller via terminals 516-520,as depicted in FIG. 17. Each Selection circuit 514 of each IC will havea local and a global address that enables it to input an instruction.The local address, as defined by the present disclosure, is an addresscapable of uniquely identifying one Selection circuit 514 within a givenIC from any other Selection circuit 514 within the same or different IC.The global address is defined as an address that commonly identifies allSelection circuits 514 within any number of ICs. All the Selectioncircuits 514 of ICs will input the address from the external controller,but only the Selection circuit 514 having an address that matches eitherthe local or global address input will be enabled to further input theinstruction. Thus Selection circuits 514 not matching the address inputwill not input the instruction. These non-addressed Selection circuit514 will be placed in an idle condition until the next address andinstruction input sequence occurs.

FIG. 7A illustrates the high level operation of the Addressable TapDomain Selection circuit 514 in response to first, second, and thirdprotocols applied to the Selection circuit 514 via terminals TCK 516,TMS/RCK 518, and TDI/TDO 520. The first protocol uses terminals TCK 516and TMS/RCK 518 to; (1) move the Selection circuit 514 from the TapDomain Access state 708 to either the Hard Reset state 702 or Soft Resetstate 704, (2) move between the Hard Reset state 702 and the Soft Resetstate 704, (3) move from the Address & Instruction input state 706 toeither the Hard 702 or Soft 704 Reset states, or (4) remain in eitherthe Hard 702 or Soft 704 Reset state. The second protocol uses terminalsTCK 516, TMS/RCK 518, and TDI/TDO 520 to move the Selection circuit 514from the Hard or Soft reset states into the Address & Instruction inputstate 706 or, if in the Address & Instruction input state 706, to remainin the Address & Input state 706. The third protocol uses terminals TCK516, TMS/RCK 518, and TDI/TDO 520 to move the Selection circuit 514 fromthe Address & Instruction Input state 706 into the Tap Domain Accessstate 708 or, if in the Tap Domain Access state 708, to remain in theTap Domain Access state 708.

Entry into the Hard reset state 702 fully resets all circuits in boththe Selection circuit 514 and the Tap domains 510 in Tap region 522.Entry into the Soft reset state 704 does not fully reset the Selectioncircuit 514 or Tap domains 510. The Hard and Soft reset states 702-704serve as starting points for communication sessions using the secondprotocol in state 706. The Hard and Soft reset states 702-704 also serveas ending points for communication sessions using the second protocol instate 706 and using the third protocol in state 708. Entry into theAddress & Instruction input state 706 starts a communication sessionusing the second protocol for inputting the above mentioned address andinstruction. Entry into the Tap Domain Access state 708 starts acommunication session using the third protocol for accessing theselected Tap Domain(s) 510.

FIG. 7B illustrates examples of “starting and stopping” sequences offirst, second, and third, and sequences of first and second protocols.

Protocol sequence A 712 illustrates the sequence of; (1) initiallyperforming a first protocol to enter into or remain in the Hard Resetstate 702, (2) switching from performing the first protocol toperforming the second protocol to cause entry into the Address &Instruction input state 706 to input an address and instruction, theinstruction in this case selecting one or more Tap Domain(s) 510 foraccess, (3) switching from performing the second protocol to performingthe third protocol to enter the Access Tap Domain state 708, foraccessing the Tap domain(s) 510 selected by the loaded instruction, and(4) switching from performing the third protocol, after the Tap domainaccess has been completed, to performing the first protocol to enter theHard Reset state 702, which terminates the protocol sequence and resetsthe Selection circuit 514 and the Tap Domains 510.

Protocol sequence B 714 illustrates the sequence of; (1) initiallyperforming a first protocol to enter into or remain in the Hard Resetstate 702, (2) switching from performing the first protocol toperforming the second protocol to cause entry into the Address &Instruction input state 706 to input an address and instruction, theinstruction in this case selecting one or more Tap Domain(s) 510 foraccess, (3) switching from performing the second protocol to performingthe third protocol to enter the Tap Domain Access state 708, foraccessing the Tap domain(s) 510 selected by the loaded instruction, and(4) switching from performing the third protocol, after the Tap domainaccess has been completed, to performing the first protocol to enter theSoft Reset state 704, which terminates the protocol sequence.

Protocol sequence C 716 illustrates the sequence of; (1) initiallyperforming a first protocol to enter into or remain in the Soft Resetstate 704, (2) switching from performing the first protocol toperforming the second protocol to cause entry into the Address &Instruction input state 706 to input an address and instruction, theinstruction in this case selecting one or more Tap Domain(s) 510 foraccess, (3) switching from performing the second protocol to performingthe third protocol to enter the Tap Domain Access state 708, foraccessing the Tap domain(s) 510 selected by the loaded instruction, and(4) switching from performing the third protocol, after the Tap domainaccess has been completed, to performing the first protocol to enter theSoft Reset state 704, which terminates the protocol sequence.

Protocol sequence D 718 illustrates the sequence of; (1) initiallyperforming a first protocol to enter into or remain in the Soft Resetstate 704, (2) switching from performing the first protocol toperforming the second protocol to cause entry into the Address &Instruction input state 706 to input an address and instruction, theinstruction in this case selecting one or more Tap Domain(s) 510 foraccess, (3) switching from performing the second protocol to performingthe third protocol to enter the Tap Domain Access state 708, foraccessing the Tap domain(s) 510 selected by the loaded instruction, and(4) switching from performing the third protocol, after the Tap domainaccess has been completed, to performing the first protocol to enter theHard Reset state 702, which terminates the protocol sequence and resetsthe Selection circuit 514 and the Tap Domains 510.

Protocol sequence E 720 illustrates the sequence of; (1) initiallyperforming a first protocol to enter into or remain in the Hard Resetstate 702, (2) switching from performing the first protocol toperforming the second protocol to cause entry into the Address &Instruction input state 706 to input an address and instruction, and (3)switching from performing the second protocol to performing the firstprotocol to enter the Hard Reset state 702, which terminates theprotocol sequence and resets the Selection circuit 514 and Tap Domains510.

Protocol sequence F 722 illustrates the sequence of; (1) initiallyperforming a first protocol to enter into or remain in the Hard Resetstate 702, (2) switching from performing the first protocol toperforming the second protocol to cause entry into the Address &Instruction input state 706 to input an address and instruction, and (3)switching from performing the second protocol to performing the firstprotocol to enter the Soft Reset state 704, which terminates theprotocol sequence.

Protocol sequence G 724 illustrates the sequence of; (1) initiallyperforming a first protocol to enter into or remain in the Soft Resetstate 704, (2) switching from performing the first protocol toperforming the second protocol to cause entry into the Address &Instruction input state 706 to input an address and instruction, and (3)switching from performing the second protocol to performing the firstprotocol to enter the Soft Reset state 704, which terminates theprotocol sequence.

Protocol sequence H 726 illustrates the sequence of; (1) initiallyperforming a first protocol to enter into or remain in the Soft Resetstate 704, (2) switching from performing the first protocol toperforming the second protocol to cause entry into the Address &Instruction input state 706 to input an address and instruction, and (3)switching from performing the second protocol to performing the firstprotocol to enter the Hard Reset state 702, which terminates theprotocol sequence and resets the Selection circuit 514 and Tap Domains510.

FIG. 8 illustrates the Addressable Tap Domain Selection circuit 514 inmore detail. The Selection circuit 514 includes a TDI/TDO I/O circuit802, a TMS/RCK I/O circuit 804, Reset, Address & Instruction controllers806, an address circuit 808, an instruction circuit 810, and a TapLinking circuit 812. The I/O circuits 802 and 804 each include an outputbuffer 814, a resistor 816, and a data input circuit 818.

The output buffer 814 of I/O circuit 802 has an input coupled to the TDOoutput signal 820 from Linking circuit 812, an output coupled to onelead of resistor 816, and a 3-state control input coupled to the outputenable 1 (OE1) signal 822 from Linking circuit 812. The other lead ofresistor 816 is coupled to the TDI/TDO terminal 520. The data inputcircuit 818 has a first input coupled to the TDI/TDO terminal 520, asecond input coupled to the TDO signal 820, and an TDI output signal 824coupled to inputs of the Address circuit 808, Instruction circuit 810,and Linking circuit 812.

The output buffer 814 of I/O circuit 804 has an input coupled to the RCKoutput signal 826 from Linking circuit 812, an output coupled to onelead of resistor 816, and a 3-state control input coupled to the outputenable 2 (OE2) signal 822 from And gate 846. The other lead of resistor816 is coupled to the TMS/RCK terminal 518. The data input circuit 818has a first input coupled to the TMS/RCK terminal 518, a second inputcoupled to the RCK signal 826, and an TMS output signal 830 coupled toinputs of the Linking circuit 812 and Controllers 806.

The Reset, Address, and Instruction Controllers 806 has inputs coupledto TCK terminal 516, TMS signal 830, an Address Match (AM) signal 838output from Address circuit 808, and to a function reset and/or power upclear signal 844. The Controller 806 outputs instruction control (IC)signals 832 to Instruction Circuit 810, an address clock (AC) signal 834to Address Circuit 808, a hard reset (HR) signal 836 to InstructionCircuit 810 and to the TRST input of Tap Domains 510 in Tap Region 522,and an Enable signal 842 to And gates 848 and 850.

And gate 850 inputs the Enable signal 842 and the TCK 516 signal andoutputs a TCK 136 signal to Tap Domains 510 in Tap Region 522. WhenEnable signal 842 is high, And gate 850 couples TCK signal 516 to TCKsignal 136. When Enable is low, TCK signal 136 is forced low.

And gate 848 inputs the Enable signal 842 and a signal 846 frominstruction output bus 840 and outputs the OE2 signal 828 to outputbuffer 814 of I/O circuit 804. When Enable signal 842 is high, And gate848 couples instruction output signal 846 to the OE2 signal 828. WhenEnable is low, OE2 828 is forced low, disabling output buffer 814 of I/Ocircuit 804. If the Tap Domain 510 selected for access is a conventionalTap Domain, i.e. no RCK, the loaded instruction will output a low oninstruction signal 846 to disable output buffer 814 from outputting RCKsignals 826 onto TMS/RCK 518 when Enable signal 842 is set high. If theTap Domain 510 selected for access is a Tap Domain that uses the RCKsignal, the loaded instruction will output a high on instruction signal846 to enable output buffer 814 for outputting RCK signals 826 ontoTMS/RCK 518 when Enable signal 842 is set high.

The Linking Circuit 812 is coupled to the I/O circuits 802-804 and tothe Controllers 806 as mentioned above. The Linking Circuit is furthercoupled to instruction output bus 840 of Instruction Circuit 810 toinput instruction control, and to the Tap Domains 510 of Tap Region 522,via signals TDI1-4 132 output, TDO1-4 140 input, TMS1-4 134 output, andRCK1-4 308 input signals.

FIG. 9 illustrates an example of how the Address Circuit 808 may bedesigned. The address circuit consists of an address shift register 902,an address compare circuit 904, and a local and global address circuit906. The shift register 902 responds to the address clock signal 834 toshift in an address from the TDI 824. The compare circuit 904 operatesto compare the address shifted into the shift register 902 to the localand global addresses output from local and global address circuit 906.The compare circuit outputs the result of the compare on the addressmatch signal 838. Since the global address will be the same for allSelection circuits 514, it will be fixed by design. The unique localaddress may be provided by the blowing of electronic fuses, an addressprogrammed into a programmable memory, an address functionally writteninto a memory, an address shifted into a shift register, an addressestablished on externally accessible device (IC/core) terminals, or byany other suitable address supplying means. A local address may notshare the same address as the global address. The compare circuit iscapable of comparing the data shifted into the address register 902against both the local address and the global address output fromaddress circuit 906. If a match occurs between the data in the addressregister 902 and the local or global address, the address match signal838 will be set high. If desired, two address match outputs, one forindicating a local address match and another for indicating a globaladdress match, could be used instead of the single address match signal838.

FIG. 10 illustrates an example of how the instruction circuit 810 may bedesigned. The instruction circuit consist of an instruction shiftregister 1002, instruction decode logic 1004, and an instruction updateregister 1006. The shift register 1002 responds to an instruction clock(I-Clock) signal from IC bus 832 to shift in an instruction from the TDI824 input. The decode logic 1004 operates to decode the instructionshifted into the shift register 1002 and to output the decode to theupdate register 1006. The update register 1006 stores the instructiondecode in response to an instruction update (I-Update) signal from ICbus 832. The stored instruction decode is output from the updateregister 1006 on instruction output bus 840. The hard reset (HR) signal836 is input to both the shift register 1002 and update register 1006 toreset the registers to known states when the hard reset signal fromController 806 is active low.

FIG. 11 illustrates an example of how the Linking Circuit 812 isinterfaced to the Tap Domains 510 of Tap Region 522. The Linking Circuit812 comprises TDI multiplexer circuitry 1102, TDO multiplexer 1104, TMSgating circuit 1110, RCK selection circuit 1106, and a Tap Trackercircuit 1114.

The TDI multiplexer circuitry 1102 comprises four individualmultiplexers for TDI1, TDI2, TDI3, and TDI4 as shown in the dotted linebox. Each individual multiplexer is coupled to TDISEL signals frominstruction output bus 840. The TDI output of each multiplexers (TDI1-TDI4) is coupled to a respective TDI input of Tap domains 1-4 510. Inresponse to the TDISEL input, the TDI multiplexers allow any of the Tapdomains to be coupled to the TDI signal 824, or to the TDO outputs (1-4)of any other Tap Domain 1-4 510. The TDO multiplexer 1104 is a singlemultiplexer that can select any of the TDO outputs (TDO1-4) from a TapDomains 1-4 510 to be coupled to the TDO signal 820 in response toTDOSEL signals from the instruction output bus 840. As can be seen,using the above described TDI and TDO multiplexer circuits, the TapDomains 1-4 510 may be individually selected between TDI 824 and TDO820, or selectively linked serially together between TDI 824 and TDO820.

TMS gating circuit 1110 receives TMSSEL1-4 signals from instructionoutput bus 840 to allow any of the TMS1-4 inputs of Tap Domain 1-4 510to be coupled to the TMS signal 830. A high on a TMSSEL signal willcouple TMS 830 to a respective TMS input of a Tap Domain 510. A low on aTMSSEL signal will force a respective TMS input of a Tap Domain 510 low.

The TCK signal 136 is coupled to all TCK inputs of Tap Domains 510. Whenthe Enable signal 842 from Reset, Address, and Instruction Controllers806 is high, TCK 136 is coupled to the TCK terminal 516 via And gate 850of FIG. 8.

The HR input 836 from Reset, Address, and Instruction Controllers 806 isinput to the TRST input of the Tap Domains 510 of Tap Region 522.

RCK selection circuit 1106 receives RCKSEL signals from instructionoutput bus 840 to allow any one or a combination of RCK 1-4 outputs ofTap Domains 1-4 510 to be coupled to the RCK signal 826. In response tothe RCKSEL signals, an RCK 1-4 from any Tap Domain 1-4 510 may becoupled to RCK 826, a combination of RCK signals may be coupled to RCK826 from voting circuit 1116, or the RCK signal 826 may be coupled to astatic logic level (a HI in this example) when no RCK is used by a TapDomain 510. The absence of an RCK signal from a Tap Domain is indicatedby dotted line. The voting circuit 1116 is used whenever two or more TapDomains each having an RCK are linked together for serial access. Inthis example, the AND gate of the voting circuit 1116 detects thecondition where both RCKs are high and the OR gate of the voting circuit1116 detects the condition where both RCKs are low. As mentionedpreviously, RCKs are handshaking signals fed back to the externalcontroller to indicate when a Tap Domain of a core have synchronized theTCK signal level input from the external controller with a functionalclock of the core.

The Tap Tracker circuit 1114 is an IEEE 1149.1 Tap state machine that isused in Linking Circuit 812 to track the states of the Tap Domain(s)being accessed in the Tap Region 522. The main function of the TapTracker 1114 is to control the output enable 1 (OE1) signal to theoutput buffer 814 of I/O circuit 802. The Tap Tracker will output asignal on OE1 to enable the output buffer to output onto terminalTDI/TDO 520 whenever the Tap Tracker (and selected Tap Domain(s)) are inthe Shift-DR or Shift-IR states (see Tap Diagram of FIG. 16). In thesestates, the selected Tap Domains will be shifting data from TDI 824 toTDO 820 and the I/O circuit 802 will be in its mode of simultaneouslyinputting and outputting this shift data on TDI/TDO terminal 520. Whennot in the Shift-DR or Shift-IR states, the Tap Domains will not beshifting data and the OE1 signal will be set to disable output buffer814 of I/O circuit 802 from operating in the simultaneous input andoutput mode on TDI/TDO terminal 520. While output buffer 814 isdisabled, I/O circuit 802 operates in an input only mode to input dataappearing of the TDI/TDO terminal 520. As seen in FIG. 11, the TapTracker inputs the TCK signal 136, the HR signal 836 (as its TRSTinput), and TMS1-4 signals via OR gate 1112.

FIG. 12 illustrates a block diagram of the Hard and Soft Resetcontroller 1202 and the Address and Instruction Controller 1204 withinthe Reset, Address, and Instruction Controllers Circuit 806. The Hardand Soft Reset controller 1202 inputs the TCK signal 516, the TMS signal830, and the functional reset and/or power up clear signal 844, andoutputs the Hard Reset (HR) 836 signal and a Soft Reset signal 1206. TheHard Reset (HR) 836 signal is input to the Instruction Circuit 810 ofFIG. 8 and the Tap Domains 510 of Tap Region 522. The Address andInstruction Controller 1204 inputs the TCK signal 516, the TMS signal830, the Address Match (AM) signal 838, and the Soft Reset signal 1206from controller 1202, and outputs the instruction control (IC) signals832 to instruction circuits 810, address clock (AC) signal 834 toaddress circuit 808, and the Enable signal 842 to And gates 848 and 850.As indicated by dotted line, the Hard and Soft Reset controllers 1202respond to the TCK 516 and TMS 830 inputs according to the previouslymentioned first protocol, and the Address and Instruction controller1204 responds to the TCK 516 and TMS 830 inputs according to thepreviously mentioned second protocol.

FIG. 13 illustrates an example of how the Hard and Soft Reset controller1202 may be designed. The Hard and Soft Reset controller 1202 consistsof two separate controllers, a hard reset controller 1302 and a softreset controller 1304. The hard reset controller 1302 consists ofinverters 1306 and 1308, Or gate 1310, and flip flop pairs 1312 and 1314connected as shown. Flip flop pairs 1312 and 1314 each include a risingedge clock flip flop feeding data to a falling edge flip flop, so ittakes both a rising and falling clock edge to propagate an input to theoutput of the pair. The soft reset controller 1304 consists of inverters1316 and 1318, flip flop pairs 1320 and 1322, and And gate 1324connected as shown. Again the flip flop pairs 1320 and 1322 include arising edge clock flip flop feeding data to a falling edge clock flipflop. In response to a low input on the function reset and/or power upclear input 844, flip flop pairs 1312 and 1314 are reset, which sets theHard Reset output 836 low and the Soft Reset output 1206 low, via Andgate 1324. In response to the function reset/power up clear 844returning high, the Hard Reset controller 1302 will remain in the resetstate (Hard Reset 836 output low) if the TCK 516 input is high and theTMS 830 input is in a stable low or high state. The Soft Resetcontroller flip flop pairs 1320 and 1322 are set while the TCK 516 inputis high.

During the operation of a second or third protocol, the TCK 516 input isactive, forcing the flip flop pairs of the Hard and Soft Resetcontrollers to be continuously forced to their set state due to the TCK516 signal being coupled to the set (S) input of the pair's flip flops.In the set state, the Hard and Soft Reset controllers output highs onthe Hard 836 and Soft 1206 Reset outputs, respectively. At the end of asecond or third protocol operation, the Hard and Soft Reset controllersmay be reset by a first protocol sequence applied on the TCK 516 and TMS830 inputs. The Soft Reset controller 1304 is always reset following asecond or third protocol operation so that a new second protocoloperation may be initiated. The Soft Reset output 1206 of the Soft Resetcontroller 1206 is used to force the Address and Instruction controller1204 to a Home state (see FIG. 14). From the Home state, another addressand instruction input operation can be performed using the secondprotocol. The Hard Reset controller 1302 is reset (Hard Reset output 836goes low) using the first protocol whenever all required second andthird protocol operations have been performed. A low on the Hard Resetoutput 836 resets the instruction circuit 810 to a known state, forcesthe Address and Instruction Controller 1204 to the Home state, andresets the Tap Domains 510 via their TRST input.

Timing diagram 1326 of FIG. 13 illustrates a first protocol sequence onTCK and TMS that will reset the Hard Reset controller 1302 and output alow on the Hard Reset signal 836 and Soft Reset signal 1206. Thesequence includes the steps of holding the TCK signal 516 high whileinputting a clock pulse or pulses on the TMS signal 830. This Hard Resetcontroller design example requires two clock pulses on the TMS signaldue to the choice of using two serially connected flip flop pairs 1312and 1314. With the TCK signal high, the rising and falling edges of thefirst TMS clock pulse sets the output of flip flop pair 1312 low and therising and falling edges of the second TMS clock pulse sets the outputof flip flop pair 1314 low, which forces the Hard Reset and Soft Resetoutputs low. The low on the Hard and Soft Reset outputs will bemaintained until the TCK signal goes low, which will set the outputs offlip flop pairs 1312 and 1314 high and the Hard and Soft Reset outputs836 and 1206 high. As indicated in dotted line, if desired, additionalTMS clock signals can occur after the Hard Reset controller 1302 hasreceived the two TMS clock pulses required to set the Hard Reset output836 low.

Timing diagram 1326 of FIG. 13 illustrates a first protocol sequence onTCK and TMS that will reset the Soft Reset controller 1304 and output alow on the Soft Reset output 1206. The sequence includes the steps ofholding the TCK signal low and inputting two clock pulses on the TMSsignal. Like the Hard Reset controller 1302 design example above, theSoft Reset controller 1304 design example uses two serially connectedflip flop pairs 1320 and 1322 for use with two TMS clock pulses. WithTCK low, the rising and falling edges of the first TMS clock pulse setsthe output of flip flop pair 1320 low and the rising and falling edgesof the second TMS clock pulse sets the output of flip flop pair 1322low, which forces the Soft Reset output 1206 low. The low on the SoftReset output 1206 will be maintained until the TCK signal goes high,which sets the outputs flip flop pairs 1320 and 1322 high and the SoftReset output 1206 high. As indicated in dotted line, if desired,additional TMS clock signals can occur after the Soft Reset controller1304 has received the two TMS clock pulses required to set the SoftReset output low.

While two TMS clock pulses were used in the Hard and Soft Resetcontroller design examples, a lesser or greater number of TMS clockpulses, and corresponding number flip flop pairs, may be used as well.Two TMS clock pulses were used in these examples because it reduces theprobability that noise or signal skew problems might accidentallyproduce the hard and soft first protocol sequences on TCK and TMS,causing the Hard and Soft controllers to inadvertently enter their resetstates. The first protocol sequence of TCK and TMS shown in the timingdiagrams 1326-1328 are TCK and TMS sequences that are never producedduring second and third protocol operations. The first protocolsequences are only detectable by the Hard and Soft Reset controllers.

FIG. 14 illustrates the state diagram of the Address and InstructionController 1204. In response to a Soft Reset output 1206 from the Hardand Soft Reset controller 1202 the Address and Instruction controller1204 will enter the Home state 1402. The Home state is maintained whileTMS is high. The controller transitions to the Input Address state 1404when TMS goes low and remains there while TMS is low. During the InputAddress state, the A-Clock 834 is active to shift in an address from TDIinto the Address circuit 808. When TMS goes high, the controller 1204transitions to the Address match state 1406 to test for a match betweenthe address shifted in and the local or global address. If the addressdoes not match the local or global address, the controller willtransition into the Idle state 1414 and remain there until a hard orsoft first protocol sequence sets the Soft Reset output 1206 low,forcing the controller to return to the Home state. If the addressmatches the local or global address, the controller 1204 transitionsinto the Input Instruction state 1408 and remains there while TMS islow. In the Input Instruction state, the I-Clock signal on IC bus 832will become active to shift in an instruction from TDI to theInstruction Circuit 810. When TMS goes high, the controller willtransition to the Update Instruction state 1410 an output the I-Updatesignal on IC bus 832 to update and output the instruction from theInstruction Circuit. When TMS goes low, the controller transitions tothe Enable state 1412. The Enable output 842 is set high during theEnable state to enable TCKs to be applied to the selected Tap Domains510. The controller will remain in the Enable state independent of logiclevels on TMS. The TMS sequences shown in FIG. 14 that move thecontroller through its states define the second protocol. While thecontroller 1204 is in the Enable state 1412, the TMS signal is operableto perform the third protocol operations to access the Tap Domains 510without effecting the Enable state 1412 of controller 1204. Thecontroller returns to the Home state 1402 only when the Soft Resetsignal 1206 goes low.

FIG. 15A illustrates an example of how the Address and Instructioncontroller 1204 of FIG. 12 may be designed. The controller 1204 consistsof; (1) a state machine 1502 having inputs for TCK 516, TMS 830, AddressMatch 838, and Soft Reset 1206, and outputs for indicating when thestate machine is in the input address state 1404, input instructionstate 1408, update instruction state 1410, and Enable state 1412, and(2) flip flops 1504-1510, and And gates 1512-1516. The state machine1502 responds to the TMS and Address Match inputs on the rising edge ofTCK 516 to move though its states. The flip flops 1512-1516 respond tothe falling edge of TCK 516 to gate the A-Clock, I-Clock, I-Updateoutput signals on an off, and to set the Enable output signal.

In response to a low on the Soft Reset input 1206, the state machine isforced to the Home state 1402. While the state machine is in the InputAddress state 1404, the A-Clock signal 834 will be gated on to clock anaddress into the Address Circuit 808. While the state machine is in theInput Instruction state 1408, the I-Clock signal 832 will be gated on toclock an instruction into the Instruction Circuit 810. While the statemachine is in the Update Instruction state 1410, the I-Update signal 832will be gated on to update the instruction from the InstructionCircuit's output bus 840. While the state machine is in the Enable state1412, the Enable output will be set high to enable Tap Domain access.

FIG. 15B illustrates an example of how the state machine 1502 may bedesigned. The state machine consists of next state decode logic 1518,state flip flops A, B, C, and output state decode logic 1520. The ABCstate assignments are shown in the FIG. 14 state diagram. If the SoftReset 1206 input is low, the state machine 1502 is reset to the Homestate (ABC=000). If the Soft Reset 1206 input is high, the state machineresponds to the rising edge of TCK to transition through its statesaccording to the state diagram of FIG. 14. The output state decode logic1520 indicates when the state machine is in the input address state 1404(ABC=001), the input instruction state 1408 (ABC=011), the updateinstruction state 1410 (ABC=100), and Enable state 1412 (ABC=101).

FIG. 16 illustrates the state diagram of the standard IEEE 1149.1 Tapcontroller. This state diagram and the design of the controller thatuses it is well known and documented in IEEE Std 1149.1 and thereforedoes not require further teaching. Each Tap Domain 510 in Tap Region 522will have a Tap controller that operates according to this standardstate diagram. The TCK and TMS operation of the standard Tap controllershown in FIG. 16 defines the third protocol of the present disclosure.

FIG. 17 illustrates a group of target devices 1702-1706 on a board orother substrate 1700, each target device including the Addressable TapDomain Selection Circuit 514 and its associated 3 pin TCK, TDI/TDO, andTMS/RCK interface, as well as Tap Domain Region 522. The target devicescould be packaged ICs or unpacked IC die. The 3 pin interface of eachtarget device is coupled to an external controller 1708 via cableconnector 1710 to provide access for test, debug, emulation, and traceoperations. Each target device 1702-1706 may contain embedded coretarget circuits 1712-1716 which also are interfaced to the externalcontroller 1708 via the 3 pin interface. Further, each core 1712-1716may contain embedded core targets circuits 1718-1722 also interfaced tothe external controller 1708 via the 3 pin interface. As indicated, theexternal controller 1708 may be realized by using an interface card 1724in a personal computer 1726 to control the 3 pin interface communicationwith the targets 1702-1706, 1712-1716, 1718-1722 via a cable connection1728. The 3 pin interface communicates to target circuits using thepreviously mentioned first, second, and third protocols.

Each target 1702-1706, 1712-1716, 1718-1722 of FIG. 17 has thepreviously mentioned local address to allow it to be individuallyaddressed and instructed by the controller 1708 using the secondprotocol. Following the individual addressing and instructing of atarget using the second protocol, the Tap Domains 510 within the targetmay be access by the controller 1708 using the third protocol to performtest, debug, emulation, and/or trace operations. Additionally, eachtarget has the previously mentioned global address to allow all targetsto be simultaneously addressed and instructed using the second protocol.The purpose of the global addressing is to allow all target devices toreceive a global instruction. The global instruction may be aninstruction that; (1) causes all targets to enter into a particular modesuitable for a test, emulation, debug, and/or trace operation, (2)causes all targets to enter into a mode to perform a global self testoperation, (3) causes all targets to suspend functional operation, or(4) causes all targets to resume functional operation. Other types ofglobal instructions may be conceived as well.

FIG. 17A illustrates an alternate configuration of FIG. 17 whereby agroup of stacked die targets devices 1732-1736 exist on a board or othersubstrate 1730. Each die in the stacks 1732-1736 includes theAddressable Tap Domain Selection Circuit 514 and its associated 3terminal TCK, TDI/TDO, and TMS/RCK interface, as well as Tap DomainRegion 522. The TCK, TDI/TDO, and TCM/RCK terminals of each die in astack are commonly connected to the TCK 1738, TMS/RCK 1740, and TDI/TDO1742 signal interface to the external controller 1708, via cableconnector 1710 to provide access for test, debug, emulation, and traceoperations. Each die in the stacks may contain embedded core targetcircuits 1712-1716 and 1718-1722 as described in FIG. 17. The controller1708 communicates to the stacked die targets using the previouslymentioned first, second, and third protocols.

Each die in a stack 1732-1736 has the previously mentioned local addressto allow it to be individually addressed and instructed by thecontroller 1708 using the second protocol. Following the individual dieaddressing and instructing, the Tap Domain 510 within the selected diemay be accessed by the controller 1708 using the third protocol toperform test, debug, emulation, and/or trace operations. Additionally,each die in stacks 1732-1736 has the previously mentioned global addressto allow all die in stacks 1732-1736 to be simultaneously addressed andinstructed using the second protocol, for the reasons mentioned inregard to FIG. 17.

FIG. 18 illustrates a group of legacy target devices 1802-1806, eachincluding the standard IEEE 1149.1 5 signal interface comprising TRST,TCK, TMS, TDI, and TDO terminals, but not the Addressable Tap DomainSelection Circuit 514. The term legacy means that the devices arepre-existing devices whose design is fixed and cannot be altered. Asshown, each legacy target device may also include the RCK terminal. Thelegacy target devices could be ICs 1802-1806 on a board or othersubstrate 1800, embedded core circuits 1802-1806 within an IC 1800, orembedded core circuits 1802-1806 within a core circuit 1800.

As seen, a separate device 1808 exists between the legacy target devices1802-1806 and the external controller 1708. This separate device 1808implements the Addressable Tap Domain Selection Circuit 514 as shown anddescribed in regard to FIG. 8 and operates according the previouslydescribed first, second, and third protocols. It also includes thepreviously described local and global addressing modes. The localaddress 1810 is shown, in this example, as being input to the separatedevice 1808 on externally accessible terminals of device 1808, which isone of the previously mentioned means for supplying the local address.The separate device 1808 serves to provide the interface between the 5signal IEEE 1149.1 terminals, and optional RCK terminal, of each legacytarget device and the 3 pin interface to the external controller 1708.The operation of the separate device 1808 in accessing the legacy deviceTap Domains is the same as described in FIG. 8 where the Addressable TapDomain Selection Circuit 514 was described accessing the Tap Domains 510of Tap Region 522.

The arrangement shown in FIG. 18 could represent the legacy targetdevices 1802-1806 and separate device 1808 as being; (1) ICs/die on aboard or substrate 1800, embedded core circuits within an IC 1800, or(3) embedded core circuits within a core circuit 1800. FIG. 18advantageously illustrates how legacy devices designed using the IEEE1149.1 interface, and optional RCK, can be interfaced to the 3 pincontroller 1708 by providing the Addressable Tap Selection Circuit 514as a separate circuit to serve as the interface between the legacydevices 1802-1806 and external controller 1708. The separate circuit1808 could contain only the Addressable Tap Domain Selection Circuit 514or it could contain the Addressable Tap Domain Selection Circuit 514along with other circuits. Indeed, the separate circuit 1808 could be alarger functional IC/die or embeddable core circuit that includes theAddressable Tap Domain Selection Circuit 514 and its external terminalinterfaces as a sub-circuit within the larger functional circuit.

FIG. 19 illustrates a group 1902 of IEEE 1149.1 legacy target devices1802-1806 as described in FIG. 18, and a group 1904 of target devices1702-1706 as described in FIG. 17. Each legacy target device 1803-1806of group 1902 is interfaced to the external controller 1708 via theseparate device 1808 as described in FIG. 18 whereas each target device1702-1706 of group 1904 is interfaced to the external controllerdirectly. This example is provided to illustrate how legacy devices1802-1806 that are not designed according to the present disclosure andother devices 1702-1704 that are designed according to the presentdisclosure can both be accessed by an external controller 1708 by usingseparate device 1808 as the interface between the legacy devices andexternal controller.

FIG. 20 illustrates the TDI/TDO signal wire connection 2002 between theTDI/TDO terminal of an I/O circuit 802 of a controller 1708 and aTDI/TDO terminal of the I/O circuits 802 of the Addressable Tap DomainSelection Circuits 514 of target circuits 1-N. The controller will haveto have the I/O circuit 802 in order to interface to and communicatewith I/O circuits 802 of the target circuits 1-N via the TDI/TDO signalwire. Preferably, the output buffer 814 of the controller 1708 and theoutput buffers 814 of the target circuits will have approximately thesame current sink/source drive strength. Also preferably the resistors816 of the controller 1708 and target circuit I/O circuits 802 will haveapproximately the same resistance.

As seen in this example, the output buffer 814 of the controller's I/Ocircuit 802 is always enabled to output TDO data to the target circuits,while the output buffers 814 of the target circuit I/O circuits 802 areselectively enabled to and disabled from outputting TDO data to thecontroller 1708 by the output enable 1 (OE1) signal 822 from Tap LinkingCircuit 812. As previously described, the TDI 824 signal of the targetI/O circuit 802 is coupled to the Address Circuit 808, the InstructionCircuit 810, and the Tap Linking Circuit 812 of Addressable Tap DomainSelection Circuit 514, and the TDO 820 signal of the target I/O circuit802 is coupled to the Tap Linking Circuit 812 of Addressable Tap DomainSelection Circuit 514. The TDI 824 signal of the controller's I/Ocircuit 802 is coupled to a circuit within the controller designed toreceive serial data input signals from TDI/TDO signal wire 2002, and theTDO 820 signal of the controller's I/O circuit 802 is coupled to acircuit within the controller designed to transmit serial data outputsignals to TDI/TDI signal wire 2002.

During first protocol operations the TDI/TDO signal wire is not used andthe output buffers of the target circuits are disabled by the OE1signals 822.

During second protocol operations when the controller 1708 is inputtingaddress and instruction signals to the target circuits 1-N, the outputbuffers 814 of the target circuits 1-N are disabled by OE1 822, allowingthe output buffer 814 of the controller to be the sole driver of theTDI/TDO signal wire 2002. Thus during second protocols the I/O circuit802 of target circuits 1-N operates as an input buffer on the TDI/TDOsignal wire 2002.

During third protocol operations when the controller 1708 is notinputting and outputting data to a selected one or more Tap Domain inthe Shift-DR or Shift-IR states, the output buffer 814 of the addressedand all other target circuits will be disabled by the OE1 signal 822. Inthis mode, the output buffer 814 of the controller is the sole driver ofthe TDI/TDO signal wire 2002.

During third protocol operations when the controller 1708 is inputtingand outputting data to a selected one or more Tap Domain in the Shift-DRor Shift-IR states, the output buffer 814 of the addressed targetcircuit will be enabled by the OE1 signal 822. In this mode, both theoutput buffers 814 of the controller and addressed target circuit willbe driving the TDI/TDO signal wire 2002. This mode of operation allowsdata to flow simultaneously between the controller 1708 and theaddressed target circuit via the TDI/TDO signal wire during each TCKperiod.

If, during this simultaneous data flow mode, the output buffer 814 ofthe controller 1708 and the output buffer 814 of the addressed targetcircuit are both outputting the same logic level, the voltage on theTDI/TDO signal wire 2002 will driven to that full logic level. The datainput circuits 818 of the controller 1708 and addressed target circuitwill detect that full logic level and input that logic level to thecontroller 1708 and to the addressed target circuit via their respectiveTDI signals 824.

If, during this simultaneous data flow mode, the output buffer 814 ofthe controller 1708 and the output buffer 814 of the addressed targetcircuit are outputting opposite logic levels, the TDI/TDO signal wire2002 will be driven to a mid point voltage level between the twoopposite logic levels. The data input circuits 818 of the controller1708 and addressed target circuit will detect that mid level voltageand, based on the logic level each was attempting to output, will inputa logic level to the controller 1708 and to the addressed target circuiton their respective TDI signal 824 that is the opposite of logic leveleach was outputting.

When the output buffers 814 of the controller and addressed targetcircuit are driving opposite logic levels on TDI/TDO wire 2002, theresistors 816 serve to limit the current flow between the two outputbuffers 814 and to serve as voltage droppers to allow the mid pointvoltage level on TDI/TDO signal wire 2002 to be more easily detected bythe data input circuit 818 as a voltage level that is distinctlydifferent from the normal full high or low logic level voltages outputfrom the output buffers 816. The operation of data input circuit 818will be described later in regard to FIG. 22.

FIG. 21 illustrates the TMS/RCK signal wire connection 2102 between theTMS/RCK terminal of an I/O circuit 804 of a controller 1708 and theTMS/RCK terminal of the I/O circuits 804 of the Addressable Tap DomainSelection Circuits 514 of target circuits 1-N. When target circuits useTap domains with RCKs, the controller will have to have the I/O circuit804 in order to interface to and communicate with I/O circuits 804 ofthe target circuits 1-N via the TMS/RCK signal wire. As with the TDI/TDOI/O circuits 802 above, the output buffers 814 of the controller andtarget circuits will preferably have approximately the same currentsink/source drive strength and the resistors 816 will have approximatelythe same resistance.

As seen in this example, the output buffer 814 of the controller isalways enabled to output TMS signals to the target circuits, while theoutput buffers 814 of the target circuits are selectively enabled to anddisabled from outputting RCK signals 826 to controller 1708 by theoutput enable 2 (OE2) signal 828. As previously described, the TMS 830signal of the target I/O circuit 804 is coupled to the Tap LinkingCircuit 812 and to the Reset, Address, & Instruction Controllers 806,and the RCK 826 signal of the target I/O circuit 804 is coupled to theTap Linking Circuit 812 of Addressable Tap Domain Selection Circuit 514.The RCK 826 signal of the controller's I/O circuit 804 is coupled to acircuit within the controller designed to receive RCK input signals fromthe TMS/RCK signal wire 2102, and the TMS 830 signal of the controller'sI/O circuit 804 is coupled to a circuit within the controller designedto transmit TMS output signals to the TMS/RCK signal wire 2102.

During first protocol operations when the controller 1708 is inputtingsoft or hard reset sequences to Hard and Soft Controller 1202, theTMS/RCK signal wire will be driven by the output buffer 814 ofcontroller 1708 and may or may not be driven by the output buffer 814 ofa target circuit 1-N. If the first protocol is performed following apower up or function reset of target circuits 1-N, the output buffers814 of the target circuits will not be enabled by OE2 and therefore onlyoutput buffer 814 of controller 1708 drives the TMS/RCK signal wire2102. Also, if a first protocol is performed following a second or thirdprotocol where the OE2 signal is set low by instruction control signal846, only the output buffer 814 of controller 1708 will be driving theTMS/RCK signal wire 2102. However, if a first protocol is performedfollowing a second or third protocol where the OE2 signal is set high byan instruction, via instruction control signal 846, both the outputbuffer 814 of controller 1708 and the output buffer of the addresstarget circuit will be driving the TMS/RCK signal wire 2102.

Following the input of a soft reset first protocol sequence, the OE2will be forced low by the Soft Reset signal 1206 from the Hard and SoftReset Controller 1202 going low. As previously mentioned, the Soft Resetsignal 1206, when low, forces the Address and Instruction controller1204 into the Home state 1402. In the Home state 1402, the Enable signaloutput 842 of the Address and Instruction controller 1204 is low, whichforces the OE2 signal 828 low via And gate 848. Thus if the outputbuffer 814 of a target circuit was enabled prior to the input of a softreset first protocol sequence, it will be disabled at the end of thesoft reset protocol sequence.

Following the input of a hard reset first protocol sequence, the OE2will be forced low by the Hard Reset signal 836 from the Hard and SoftReset Controller 1202 going low. When Hard Reset signal 836 goes low,the instruction circuit 810 is reset to an instruction that sets theinstruction control output signal 846 low which forces the OE2 output828 of And gate 848 low. Also the Hard Reset signal going low will setthe Soft Reset signal 1206 low, via And gate 1324 of FIG. 13, which setsthe Enable signal 842 low and the OE2 output of And gate 848 low. Thusif the output buffer 814 of a target circuit was enabled prior to theinput of a hard reset first protocol sequence, it will be disabled atthe end of the soft reset protocol sequence.

During second protocol operations when the controller 1708 is inputtingaddress and instruction signals to the target circuits 1-N, the outputbuffers 814 of the target circuits 1-N are disabled by OE2 828 beinglow, allowing the output buffer 814 of the controller to be the soledriver of the TMS/RCK signal wire 2102. Thus during second protocols theI/O circuits 804 of target circuits 1-N operate as an input buffers onthe TMS/RCK signal wire 2102.

During third protocol operations when the controller 1708 iscommunicating to a selected one of more Tap Domains of target circuitsthat do not use RCKs, the output buffer 814 of the addressed and allother target circuits will be disabled by the OE2 signal 828 being low.In this mode, the output buffer 814 of the controller is the sole driverof the TMS/RCK signal wire 2102.

During third protocol operations when the controller 1708 iscommunicating to a selected one of more Tap Domains of target circuitsthat use RCKs, the output buffer 814 of the addressed target circuitwill be enabled by its OE2 signal 828 being high and the output buffer814 of all other target circuits will be disabled by their OE2 signals828 being low. In this mode, the output buffer 814 of the controller andthe output buffer 814 of the addressed target circuit will both bedriving the TMS/RCK signal wire 2102. In this mode of operation, a TMSsignal can flow from the controller 1708 to the addressed target circuitand an RCK signal can flow from the addressed target circuit to thecontroller 1708 simultaneously via TMS/RCK signal wire 2102 during eachTCK period.

If, during this simultaneous TMS and RCK signal flow mode, the outputbuffer 814 of the controller 1708 and the output buffer 814 of theaddressed target circuit are both outputting the same logic level, thevoltage on the TMS/RCK signal wire 2102 will driven to that full logiclevel. The data input circuits 818 of the controller 1708 and addressedtarget circuit will detect that full logic level and input that logiclevel to the controller 1708 via its RCK 826 and to the addressed targetcircuit via its TMS signal 830. If, during this simultaneous data flowmode, the output buffer 814 of the controller 1708 and the output buffer814 of the addressed target circuit are outputting opposite logiclevels, the TMS/RCK signal wire 2102 will be driven to a mid pointvoltage level between the two opposite logic levels. The data inputcircuits 818 of the controller 1708 and addressed target circuit willdetect that mid level voltage and, based on the logic level each wasattempting to output, will input a logic level to the controller 1708 onits RCK 826 and to the addressed target circuit on its TMS 830 that isthe opposite of logic level each was outputting.

When the output buffers 814 of the controller and addressed targetcircuit are driving opposite logic levels on TMS/RCK wire 2102, theresistors 816 serve to limit the current flow between the two outputbuffers 814 and to serve as voltage droppers to allow the mid pointvoltage level on TMS/RCK signal wire 2102 to be more easily detected bythe data input circuit 818 as a voltage level that is distinctlydifferent from the normal full high or low logic level voltages outputfrom the output buffers 814.

FIG. 22 illustrates one example of how to design the data input circuit818 of the I/O circuit 802 and 804. The data input circuit 818 includesa voltage comparator circuit 2202, a multiplexers 2204, an inverter2206, and a buffer 2208. The voltage comparator circuit 2202 inputsvoltages from its wire input 2210 and outputs digital control signals S0and S1 to multiplexer 2204. The wire input 2210 for I/O circuit 802 iscoupled to the TDI/TDO signal wire 2002 of FIG. 20 via TDI/TDO terminalsof the controller 1708 and target circuits 1-N. The wire input 2210 forI/O circuit 804 is coupled to the TMS/RCK signal wire 2102 of FIG. 21via TMS/RCK terminals of controller 1708 and target circuits 1-N.

As seen, the first voltage (V) to ground (G) leg 2218 of voltagecomparator circuit 2202 comprises a series P-channel transistor andcurrent source and the second voltage to ground leg 2220 comprises aseries N-channel transistor and current source. As seen, S1 is connectedat a point between the P-channel transistor and current source of thefirst leg 2218 and S0 is connected at a point between the N-channeltransistor and current source of the second leg 2220. The gates of thetransistors are connected to wire input 2210 to allow voltages on thewire signal 2210 to turn the transistors on and off.

The operation of the voltage comparator circuit 2202 and multiplexer2204 is shown in table 2222 and described herein. If the voltage on wireinput 2210 is at a low level (logic zero), the S0 and S1 outputs are sethigh, which causes the multiplexer 2204 to select its low input 2224 andoutput the low input to In signal 2212 via buffer 2208. If the voltageon wire input 2210 is at a mid level (mid point voltage), the S0 is setlow and the S1 is set high, which causes the multiplexer 2204 to selectits Out* input 2226 (inverted Out signal 2214) and output the Out* inputto In 2212 via and buffer 2208. If the voltage on wire connection 2210is high (logic one), the S0 and S1 outputs are set low, which causes themultiplexer 2204 to select its high input 2228 and output the high inputto In 2212 via and buffer 2208.

For I/O circuits 802, the In signal 2212 is connected to the TDI signal824 of the controller 1708 and Addressable Tap Domain Selection Circuits514 of target circuits 1-N of FIG. 20, and the Out signal 2214 isconnected to the TDO signal 820 of the controller 1708 and AddressableTap Domain Selection Circuits 514 of target circuits 1-N of FIG. 20.

For I/O circuits 804, the In signal 2212 is connected to the RCK signal826 of the controller 1708 and to the TMS signal 830 of the AddressableTap Domain Selection Circuits 514 of target circuits 1-N of FIG. 21. TheOut signal 2214 is connected to the TMS signal 830 of the controller1708 and to the RCK signal 826 of the Addressable Tap Domain SelectionCircuits 514 of target circuits 1-N of FIG. 21.

FIG. 23A illustrates the case where the output buffers 814 of thecontroller 1708 and an addressed target circuit are both outputtinglogic lows on TDI/TDO 2002 or TMS/RCK 2102 signal wires. In this casethe signal wire 2002/2102 is low and the wire input 2210 to the datainput circuits 818 is low. This causes the data input circuit 818 of thecontroller 1708 to input a low to the controller on In signal 2212 andthe data input circuit 818 of the addressed target circuit to input alow to the target circuit on In signal 2212.

FIG. 23B illustrates the case where the output buffer 814 of thecontroller 1708 is outputting a low on signal wire 2002/2102 and theoutput buffer 814 of an addressed target circuit is outputting a high onsignal wire 2002/2102. In this case a current path exists from the highvoltage output (V) from the target circuit to the low voltage output (G)from the controller. The resistors 816 limit the current flow and thevoltage drops across them produce a distinctly detectable mid pointvoltage level on the signal wire 2002/2102. The mid point voltage levelon the signal wire 2002/2102 is input to the data input circuits 818 ofthe controller and target circuit via wire inputs 2210.

Since the data input circuit 818 of the controller 1708 knows thecontroller was outputting a logic low, it responds to the mid pointvoltage by inputting a logic high to the controller on In signal 2212,which is the only logic level that can be output from the target circuitto cause the mid point voltage on signal wire 2002/2102. Also since thedata input circuit 818 of the target circuit knows the target circuitwas outputting a logic high, it responds to the mid point voltage byinputting a logic low to the target circuit on In signal 2212, which isthe only logic level that can be output from the controller to cause themid point voltage on signal wire 2002/2102.

FIG. 23C illustrates the case where the output buffer 814 of thecontroller 1708 is outputting a high on signal wire 2002/2102 and theoutput buffer 814 of an addressed target circuit is outputting a low onsignal wire 2002/2102. In this case a current path exists from the highvoltage output (V) from the controller to the low voltage output (G)from the addressed target circuit. Again the resistors 816 limit thecurrent flow and the voltage drops across them produce a distinctlydetectable mid point voltage level on the signal wire 2002/2102. The midpoint voltage level on the signal wire 2002/2102 is input to the datainput circuits 818 of the controller and target circuit via wire inputs2210.

Since the data input circuit 818 of the controller 1708 knows thecontroller was outputting a logic high, it responds to the mid pointvoltage by inputting a logic low to the controller on In signal 2212,which is the only logic level that can be output from the target circuitto cause the mid point voltage on signal wire 2002/2102. Also since thedata input circuit 818 of the target circuit knows the target circuitwas outputting a logic low, it responds to the mid point voltage byinputting a logic high to the target circuit on In signal 2212, which isthe only logic level that can be output from the controller to cause themid point voltage on signal wire 2002/2102.

FIG. 23D illustrates the case where the output buffers 814 of thecontroller 1708 and an addressed target circuit are both outputtinglogic high on signal wire 2002/2102. In this case the signal wire2002/2102 is high and the wire input 2210 to the data input circuits 818is high. This causes the data input circuit 818 of the controller 1708to input a high to the controller on In signal 2212 and the data inputcircuit 818 of the addressed target circuit to input a high to thetarget circuit on In signal 2212.

FIG. 24 illustrates timing waveforms 2402 for the four cases (A,B,C,D)in which simultaneous data communication occurs between the I/O circuit802/804 of controller 1708 and the I/O circuit 802/804 of an AddressableTap Domain Selection Circuit 514 of an addressed target circuit via aTDI/TDO or TMS/RCK signal wire 2002/2102. In this example, the outputenable 1 or 2 (OE1/OE2) signal 822/828 of the target circuit is set toenable output buffer 814. Each case A-D is indicated in the timingdiagram by vertical dotted line boxes.

Case A shows the controller and the target circuit outputting lows fromtheir buffers 814. In response, the wire 2002/2102 is low and both thecontroller and target circuit input lows via the In signal 2212 fromtheir data input circuits 818.

Case B shows the controller outputting a low from its buffer 814 and thetarget circuit outputting a high from its buffer 814. In response, thewire 2002/2102 is at a mid voltage level causing the controller to inputa high from the In signal 2212 of its data input circuit 818, while thetarget circuit inputs a low from the In signal 2212 of its data inputcircuit 818.

Case C shows the controller outputting a high from its buffer 814 andthe target circuit outputting a low from its buffer 814. In response,the wire 2002/2102 is at a mid voltage level causing the controller toinput a low from the In signal 2212 of its data input circuit 818, whilethe target circuit inputs a high from the In signal 2212 of its datainput circuit 818.

Case D shows the controller and the target circuit outputting high fromtheir buffers 814. In response, the wire 2002/2102 is high and both thecontroller and target circuit input highs via the In signal 2212 fromtheir data input circuits 818.

FIG. 25 illustrates a timing diagram of the operation of the presentdisclosure performing a first protocol Soft Reset Sequence 1328 followedby a second protocol showing entry into the Home state 1402 followed byentry into the Input Address state 1404.

FIG. 26 illustrates a timing diagram of the operation of the presentdisclosure performing a first protocol Soft Reset Sequence 1328 followedby a second protocol that immediately enters the Input Address state1404.

FIG. 27 illustrates a timing diagram of the operation of the presentdisclosure performing a first protocol Hard Reset Sequence 1326 followedby a second protocol showing entry into the Home state 1402 followed byentry into the Input Address state 1404.

FIG. 26 illustrates a timing diagram of the operation of the presentdisclosure performing a first protocol Hard Reset Sequence 1326 followedby a second protocol that immediately enters the Input Address state1404.

FIG. 29 illustrates a timing diagram of the operation of the presentdisclosure performing a full second protocol sequence 2902 of inputtingan address 1404, matching the address 1406, inputting an instruction1408, updating the instruction 1410, and entering the enable state 1412,followed by performing a third protocol sequence 2904 to access the Tapdomain(s) 510 selected by the instruction using the standard IEEE 1149.1TMS protocol, followed by performing a first protocol sequence 2906 toinput either a Soft Reset sequence 1328 or a Hard reset sequence 1326 toterminate the operation.

As seen, the second protocol 2902 uses the TCK 516, TMS 830, and TDI 824signals, but not the TDO 820 signal. The third protocol 2904 uses theTCK 516, TMS 830, TDI 824, and TDO 820 signals according to the Tapprotocol defined in standard IEEE 1149.1. The first protocols 2906 (1328and 1326) use only the TCK 516 and TMS 830 signals. The timing diagramof FIG. 29 illustrates in detail the present disclosure performing thepreviously described protocols A-D 712-718 sequences discussed early inregard to FIG. 7B.

FIG. 30 illustrates a timing diagram of the operation of the presentdisclosure performing a full second protocol sequence 2902 of inputtingan address 1404, matching the address 1406, inputting an instruction1408, updating the instruction 1410, and entering the enable state 1412,followed by performing a first protocol sequence 2906 to input either aSoft Reset sequence 1328 or a Hard reset sequence 1326 to terminate theoperation.

As seen, the second protocol 2902 uses the TCK 516, TMS 830, and TDI 824signals, but not the TDO 820 signal. The first protocols 2906 (1328 and1326) use only the TCK 516 and TMS 830 signals. The timing diagram ofFIG. 30 illustrates in detail the present disclosure performing thepreviously described protocols E-H 720-726 sequences discussed early inregard to FIG. 7B.

While the description of the disclosure to this point has shown that thedisclosure includes an Addressable Tap Domain Selection Circuit 514capable of selecting one or more of a plurality of Tap Domains 510within a Tap Region 522 (FIGS. 6 and 8) using a reduced number ofinterface signals, it is possible to simplify the disclosure when accessto only one JTAG circuit Tap Domain is required. A reduction ofinterface signals is achieved in the simplified version of thedisclosure.

FIG. 31 illustrates a connected controller 3102 accessing theconventional JTAG circuit 104 of FIG. 1 using the 5 IEEE 1149.1 standardsignals TDI, TDO, TMS, TCK, and TRST. The JTAG circuit 104 could be usedin an IC or core for controlling test, debug, emulation, trace, boundaryscan, or other operations of the IC or core.

FIG. 32 illustrates I/O circuits 802 of the present disclosure beingused to reduce the signal interface between the connected controller3102 and JTAG circuit 104 from 5 to 4 signals. One I/O circuit 802 isconnected to the controller's TDO output via Out signal 2214, to thecontrollers TDI input via In signal 2212, and to the TDI/TDO signal wire3202 via Wire signal 2210. The other I/O circuit 802 is connected to theJTAG circuit's TDO output via Out signal 2214, to the JTAG circuit's TDIinput via In signal 2212, and to the TDI/TDO signal wire 3202 via Wiresignal 2210.

As seen in FIG. 32, the I/O circuit 802 associated with the controllercan exist as a separate circuit from the controller 3102 or the I/Ocircuit 802 may be integrated with the controller 3102 to form a newcontroller 3204. Preferably, but not necessarily, the output buffer 814of the I/O buffer associated with the controller 3102 will be enabledall the time by setting its output enable signal 822 high, which allowsthe TDI/TDO wire 3202 to a always be driven to a valid signal level.

Also as seen in FIG. 32, the I/O circuit 802 associated with the JTAGcircuit 104 can exist as a separate circuit from the JTAG circuit 104 orthe I/O circuit 802 may be integrated with the JTAG circuit 104 to forma new JTAG circuit 3206. If the I/O circuit 802 associated with the JTAGcircuit is a separate circuit, its output buffer 814 will be enabled,via output enable signal 822, all the time since their is no signalavailable from the JTAG circuit 104 to act as an enable or disablesignal to the output buffer 814. If the I/O circuit 802 associated withthe JTAG circuit 104 is integrated with the JTAG circuit 104 to form newJTAG circuit 3206, the output enable 822 of the I/O circuit 802 will beconnected to the JTAG's Enable signal 126 so that the output buffer 814can be enabled during TDI and TDO shift operations and disabled duringnon shift operations.

The Enable signal 126 is a standard signal output from Tap controller120 during data and instruction shift operations. The Enable signal 126controls the enable and disable state of the JTAG circuit's TDO tristateoutput buffer 128. If the I/O circuit 802 is integrated with JTAGcircuit 104 to form new JTAG circuit 3206 it is preferred that the TDOtristate buffer 128 be removed, as indicated by crossed dashed lines, sothat the TDO signal path formed between flip flop 124 and Out signal2214 of I/O circuit 802 does not enter into a tristate (floating) statewhen shift operations are not being performed.

FIG. 33 illustrates a connected controller 3302 accessing the JTAGcircuit 302 of FIG. 3 using the 5 IEEE 1149.1 standard signals TDI, TDO,TMS, TCK, and TRST plus the non-standard RCK signal. The JTAG circuit302 could be used in an IC or core for controlling test, debug,emulation, trace, boundary scan, or other operations of the IC or core.

FIG. 34 illustrates I/O circuits 802 and 804 of the present disclosurebeing used to reduce the signal interface between the connectedcontroller 3302 and JTAG circuit 302 from 6 to 4 signals. The connectionand operation of I/O circuits 802 associated with controller 3302 andJTAG circuit 302 are the same as described previously in FIG. 32 in thefollowing separate and integrated implementation descriptions of I/Ocircuit 804. One I/O circuit 804 is connected to the controller's TMSoutput via Out signal 2214, to the controllers RCK input via In signal2212, and to the TMS/RCK signal wire 3402 via Wire signal 2210. Theother I/O circuit 804 is connected to the JTAG circuit's RCK output viaOut signal 2214, to the JTAG circuit's TMS input via In signal 2212, andto the TMS/RCK signal wire 3402 via Wire signal 2210.

As seen in FIG. 34, the I/O circuit 804 associated with the controllercan exist as a separate circuit from the controller 3302 or the I/Ocircuit 804 may be integrated with the controller 3302 to form a newcontroller 3404. Preferably, but not necessarily, the output buffer 814of the I/O buffer associated with the controller 3302 will be enabledall the time by setting its output enable signal 822 high, which allowsthe TMS/RCK wire 3402 to a always be driven to a valid signal level.

Also as seen in FIG. 34, the I/O circuit 804 associated with the JTAGcircuit 302 can exist as a separate circuit from the JTAG circuit 302 orthe I/O circuit 804 may be integrated with the JTAG circuit 302 to forma new JTAG circuit 3406. Regardless of whether I/O circuit 804 is aseparate circuit or integrated with JTAG circuit 302, its output buffer814 will be enabled, by setting its output enable signal 822 high, allthe time since the RCK signal of JTAG circuit 302 must always be outputto the controller 3302 during test, debug, emulation, trace, and/orother operations.

From the above examples shown in FIG. 31-34, it is clear that the I/Ocircuits 802-804 of the present disclosure can be used to provide amethod of reducing the interface signals between a controller 3102,3204, 3302, and 3404 and a JTAG circuit 104, 3206, 302, and 3406. Whilethe access approach described in FIGS. 31-34 is a point-to-point accessbetween a controller and a connected JTAG circuit, i.e. it does notprovide the multiple JTAG circuit Tap Domain selecting features asdescribed earlier in the present disclosure, it does offer a reducedsignal interfacing approach which is simple and can be realized with aminimum of additional circuitry.

FIG. 35 illustrates an IC or core 3504 containing the emulation, trace,and/or debug circuit 106 of FIG. 1 coupled internally to a functionalcircuit 102 of the IC or core via bus 112 and externally to anemulation, trace, and/or debug interface 3506 of a controller 3502 viabus 110. The bus 110 consists of input and output connections forallowing signals to flow between circuit 3506 and 106 during anemulation, trace, and/or debug operation. In this example, 8 connectionsare used on bus 110.

The signals could be control signals, data signals, triggering signals,protocol signals used in message communications, and/or other signalsused during an I/O operation of an emulation, trace, and/or debugoperation. To increase the bandwidth of signal flow between the IC/core3504 and controller 3502 it is advantageous to have as many input andoutput signals on bus 110 as possible. However, only so many ICterminals may be used on bus 110, since the IC's functional input andoutput terminals 103 take priority and therefore will consume most ofthe available IC input and output terminals.

FIG. 36 illustrates how the controller 3502 and IC/core 3504 of FIG. 35can be adapted with I/O circuits 802 of the present disclosure to reducethe number of signal connections between the controller and IC/core byone half without reducing the signaling bandwidth.

As seen in FIG. 36, controller circuit 3602 differs from controllercircuit 3502 of FIG. 35 in that the input and output signals of bus 110to emulation, trace, and debug circuit 3506 are interfaced to I/Ocircuits 802, via the I/O circuit's input 2214 and output 2212. Ifdesired, circuit 3506 may optionally be modified, as seen in dottedline, to allow inputting control to the 802 I/O circuit's output enablesignal 822, otherwise the output enable 822 input of I/O circuit 802will be fixed to always enable the output buffer 814 of I/O circuit 802.

Similarly, the IC/core circuit 3604 differs from IC/core circuit 3504 inthat the input and output signals of bus 110 to emulation, trace, anddebug circuit 106 are interfaced to I/O circuits 802, via the I/Ocircuit's input 2214 and output 2212. If desired, circuit 106 mayoptionally be modified, as seen in dotted line, to allow inputtingcontrol to the 802 I/O circuit's output enable signal 822, otherwise theoutput enable 822 input of I/O circuit 802 will be fixed to alwaysenable the output buffer 814 of I/O circuit 802.

As seen in FIG. 36, the number of bus 3606 connections, via wireterminals 2210 of the I/O circuits 802 of circuits 3602 and 3604, isreduced by one half of that shown in bus 110 of FIG. 35. Thus, thepresent disclosure provides a way of reducing the number of requiredemulation, debug, and/or trace signal connections between circuits 3602and circuits 3604 of FIG. 36 on bus 3606 by one half that used in theprior art of FIG. 35.

The following FIGS. 37-40 are provided to illustrate how the I/Ocircuits 802 (or 804) can be used to reduce the functional signalconnections between functional circuits of an IC or core circuit.

FIG. 37 illustrates ICs or cores 3702 and 3704 each containing thefunctional circuit 102 of FIG. 1. At least some of the functionalcircuits 102 inputs and outputs are coupled to each other via functionalbus 103 of FIG. 1. The bus 103 consists of input and output connectionsfor allowing signals to flow between functional circuits 102 duringfunctional operation. In this example, 8 connections are used on bus103. The signals could be data bus signals, address bus signals, orcontrol bus signals used during functional communicating betweenfunctional circuits 102.

FIG. 38 illustrates how the functional circuits 102 of ICs or cores 3702and 3704 can be adapted with I/O circuits 802 of the present disclosureto reduce the number of signal connections on functional bus 103 betweenthe functional circuits 102. As seen, the functional bus 3806 betweenthe adapted ICs or cores 3802 and 3804 require only one half theconnections required by functional bus 103 of FIG. 37. Also functionalbus 3806 maintains the signaling bandwidth of functional bus 103 of FIG.37.

As seen in FIG. 38, IC or core circuits 3802 and 3804 differ from IC orcore circuits 3702 and 3704 of FIG. 37 in that the input and outputsignals of bus 103 to functional circuits 102 are interfaced to I/Ocircuits 802, via the I/O circuit's input 2214 and output 2212. Also asseen, functional circuits 102 in IC or core circuits 3802 and 3804 mayoptionally be modified, as seen in dotted line, to allow inputtingcontrol to the 802 I/O circuit's output enable signal 822, otherwise theoutput enable 822 input of I/O circuit 802 will be fixed to alwaysenable the output buffer 814 of I/O circuit 802.

As seen in FIG. 38, the number of bus 3806 connections, via wireterminals 2210 of the I/O circuits 802 of circuits 3802 and 3804, isreduced by one half of that shown in bus 103 of FIG. 37. Thus, thepresent disclosure provides a way of reducing the number of requiredfunctional signal connections between IC or core circuits 3802 and 3804of FIG. 38 on bus 3806 by one half that used in the prior art functionalbus 103 of FIG. 37.

FIG. 39 illustrates conventional ICs 3902, 3908, 3912 on aboard/substrate or core circuits 3902, 3908, 3912 within an IC beingconnected functionally together via functional bus 103 and select andcontrol bus 3906. IC/core 3902 contains a master functional circuit3904, such as a processor or DSP, that controls communication to slavefunctional circuits 3910 and 3914, such as memories or other types ofinput and output circuits, in IC/cores 3908 and 3912 via buses 103 and3906. In this example, the select and control bus 3906 from the masterfunctional circuit functions as a bus that selects a functional slavecircuit 3910 or 3914 then inputs control to cause the selected slavecircuit to input data from the master circuit or to output data to themaster circuit via bus 103. The functional bus 103 in this example is 8signals wide.

FIG. 40 illustrates how the functional circuits 3904, 3910, 3914 can beadapted with I/O circuits 802 of the present disclosure to reduce thenumber of signal connections on functional bus 103 between thefunctional circuits. As seen, the functional bus 4008 between theadapted ICs or cores 4002, 4004, 4006 require only one half theconnections required by functional bus 103 of FIG. 39. Also functionalbus 4008 maintains the signaling bandwidth of functional bus 103 of FIG.39.

As seen in FIG. 40, IC or core circuits 4002-4006 differ from IC or corecircuits 3902, 3908, and 3912 of FIG. 39 in that the input and outputsignals of bus 103 to functional circuits 3904, 3910, 3914 areinterfaced to I/O circuits 802, via the I/O circuit's input 2214 andoutput 2212. Also as seen, the master functional circuit 3904 of IC/corecircuit 4002 may optionally be modified, as seen in dotted line, toallow inputting control to the 802 I/O circuit's output enable signal822, otherwise the output enable 822 input of I/O circuit 802 will befixed to always enable the output buffer 814 of I/O circuit 802.Providing the ability to disable the output buffer 814 of I/O circuits802 connected to master functional circuit 2904 in IC/core circuit 4002allows for the output buffers 814 of a selected slave functionalcircuit's I/O circuits 802, say slave circuit 3910, to be enabled todrive the bus 4008 to communicate data to another one or more of theslave functional circuits, say slave circuit 3914.

As seen in FIG. 40, the number of bus 4008 connections, via wireterminals 2210 of the I/O circuits 802 of circuits 4002, 4004, 4008, isreduced by one half of that shown in bus 103 of FIG. 39. Thus, thepresent disclosure provides a way of reducing the number of requiredfunctional signal connections between IC or core circuits 4004-4006 ofFIG. 40 on bus 4008 by one half that used in the prior art functionalbus 103 of FIG. 39.

While the preceding description has shown and described the AddressableTap Domain Selection Circuit 514 as having a 3 pin interface consistingof TCK, TMS/RCK, and TDI/TDO signals, the Addressable Tap DomainSelection Circuit 514 may be designed to use the standard IEEE 1149.1TDI, TDO, TMS, and TCK signals, plus the non-standard RCK signal.

FIG. 41 illustrates an Addressable Tap Domain Selection circuit 4102that has been designed in an IC or core to use the standard IEEE 1149.1interface signals TDI, TDO, TMS, TCK, and non-standard RCK signal. Theonly difference between the Addressable Tap Domain Selection circuit4102 and the Addressable Tap Domain Selection circuit 514 of FIG. 8 isthat the I/O circuits 802 and 804 have been removed and the TDI 824, TDO820, TMS 830, and RCK 826 signals have been coupled, via buffers4104-4110, to externally accessible signal terminals TDI 4112, TDO 4114,TMS 4116, and RCK 4118, respectively.

The operation of Addressable Tap Domain Selection circuit 4102, inresponse to the first, second, and third protocols, is identical to thatpreviously described with Addressable Tap Domain Selection circuit 514.For example, the first protocol uses TCK and TMS 830 as previouslydescribed for Hard and Soft resets, the second protocol uses TCK, TMS830, and TDI 824 as previously described for loading address andinstruction, and the third protocol uses TCK, TMS 830, TDI 824, and TDO820 as previously described to access Tap domains. The only differenceis that is that TDI 824 is coupled to a TDI input terminal 4112 insteadof I/O circuit 802, TDO 820 is coupled to a TDO output terminal 4114instead of I/O circuit 802, and TMS 830 is coupled to a TMS inputterminal 4116 instead of I/O circuit 804. Also the RCK 826 is coupled toRCK output terminal 4118 instead of I/O circuit 804.

As seen, the control input of output buffer 4106 is coupled to OE1 822to enable TDO output during shift operations and to disable TDO outputduring non-shift operations during third protocol (JTAG) operations.Also, the control input of output buffer 4110 is coupled to OE2 enableor disable RCK outputs during third protocol (JTAG) operations.

FIG. 42 illustrates a group of target devices 4202-4206 on a board orother substrate 4200, each target device including the Addressable TapDomain Selection Circuit 4102 and its associated 5 pin TCK, TDI, TDO,TMS, and RCK interface, as well as Tap Domain Region 522. The targetdevices could be packaged ICs or unpackaged IC die. The 5 pin interfaceof each target device is coupled to an external controller 4208 viacable connector 4210 to provide access for test, debug, emulation, andtrace operations. Each target device 4202-4206 may contain embedded coretarget circuits as described in FIG. 17, which also are interfaced tothe external controller 4208 via the 5 pin interface. As indicated, theexternal controller 4208 may be realized by using an interface card 4212in a personal computer 1726 to control the 5 pin interface communicationwith the targets 4202-4206 via a cable connection 4214. The 5 pininterface communicates to target circuits using the previously mentionedfirst, second, and third protocols.

Each target 4202-4206 has the previously mentioned local address toallow it to be individually addressed and instructed by the controller4208 using the second protocol. Following the individual addressing andinstructing of a target using the second protocol, the Tap Domains 510within the target may be accessed by the controller 4208 using the thirdprotocol to perform test, debug, emulation, and/or trace operations.Additionally, each target has the previously mentioned global address toallow all targets to be simultaneously addressed and instructed usingthe second protocol for the purposes previously mentioned in regard toFIG. 17.

When a target is selected for a third protocol (JTAG) communication toone or more of its Tap Domains, its TDO 4114 terminal will be enabled byOE1 to output TDO 820 data from the Tap Domain(s) during the 1149.1Shift-IR and Shift-DR states as previously mentioned. During thirdprotocol (JTAG) operations to Tap Domains with RCK signals, the RCK 4118terminal will be enabled by OE2 to output RCK 826 signals to thecontroller 4208. During third protocol (JTAG) operations to Tap Domainswithout RCK signals, the RCK 4118 terminal will be disabled by OE2 tonot output RCK 826 signals to the controller 4208.

Only the addressed target circuit will be enabled to output on its TDO4114 and RCK 4118 terminals. The TDO 4114 and RCK 4118 terminals ofnon-addressed target circuits will be disabled, via control signals OE1and OE2 to buffers 4106 and 4110, so that only the addressed targetdevice is enabled to drive the TDO and RCK signal connections to thecontroller 4208.

FIG. 43 illustrates the legacy target devices 1802-1806 of FIG. 18, eachincluding the standard IEEE 1149.1 TRST, TCK, TMS, TDI, and TDOterminals, and optionally the non-standard RCK terminal. The legacytarget devices could be ICs 1802-1806 on a board or other substrate4300, embedded core circuits 1802-1806 within an IC 4300, or embeddedcore circuits 1802-1806 within a core circuit 4300.

As seen, a separate device 4302 exists between the legacy target devices1802-1806 and the external controller 4208. This separate device 4302implements the Addressable Tap Domain Selection Circuit 4102 of FIG. 41and operates according the previously described first, second, and thirdprotocols. It also includes the previously described local and globaladdressing modes. The local address is shown, in this example, as beinginput to the separate device 4302 on externally accessible terminals ofdevice 4302. The separate device 4302 serves to provide the interfacebetween the JTAG plus RCK interface of each legacy target device and the5 signal interface to the external controller 4208. The operation of theseparate device 4302 in accessing the legacy device Tap Domains is thesame as described in FIG. 41 where the Addressable Tap Domain SelectionCircuit 4102 was described accessing the Tap Domains 510 of Tap Region522.

The arrangement shown in FIG. 43 could represent the legacy targetdevices 1802-1806 and separate device 4302 as being; (1) ICs/die on aboard or substrate 4300, embedded core circuits within an IC 4300, or(3) embedded core circuits within a core circuit 4300. FIG. 43advantageously illustrates how legacy devices designed using theconventional IEEE 1149.1 interface and optional RCK can be interfaced tothe 5 signal controller 4208 by providing the Addressable Tap SelectionCircuit 4102 as a separate circuit to serve as the interface between thelegacy devices 1802-1806 and external controller 4208. As described forseparate circuit 1808 of FIG. 18, the separate circuit 4302 couldcontain only the Addressable Tap Domain Selection Circuit 4102 or itcould contain the Addressable Tap Domain Selection Circuit 4102 alongwith other circuits.

There may be instances where it may be desirable to select between usinga 5 signal interface to an Addressable Tap Domain Selection circuit asshown FIG. 41 and a 3 signal interface to an Addressable Tap DomainSelection circuit as shown in FIG. 8. For example, for test operationsit may be advantageous to use the 5 signal interface to enable standardJTAG communication from pre-existing JTAG controllers and testersdesigned to operate according to the standard JTAG interface andoptional non-standard RCK signal. On the other hand, it may beadvantageous to use the 3 signal interface during debug, emulation, andtrace operations so that unused signals of the 5 signal interface may beused for other purposes.

FIG. 44 illustrates an Addressable Tap Domain Selection circuit 4402that has been designed in an IC or core to selectively use either the 5signal interface of FIG. 41 or the 3 signal interface of FIG. 8. TheAddressable Tap Domain Selection circuit 4402 is the same as thatdescribed in FIGS. 8 and 41 with the exception that an Interface SelectCircuit 4404 has been substituted for the I/O circuits 802 and 804 ofFIG. 8 and the input and output buffers 4104-4110 of FIG. 41. TheInterface Select Circuit 4404 has input terminals for receiving control4416 from the instruction output bus, TDO signal 820, OE1 signal 822,RCK signal 826, and OE2 signal 828. The Interface Select Circuit 4404has output terminals for outputting TDI signal 824 and TMS signal 830.The Interface Select Circuit 4404 has input and output terminals for anauxiliary I/O bus (AUXI/O) 4406. The interface Select circuit 4404 hasI/O terminals for an “AUXI/O1 or TDI” signal 4408, “TDI/TDO or TDO”signal 4410, “AUXI/O2 or TMS” signal 4412, and “TMS/RCK or RCK” signal4414.

The function of the Interface Select Circuit 4402 is to respond tocontrol inputs 4416 from the instruction register output bus to operateas either a 5 signal interface or as a 3 signal interface to theAddressable Tap Domain Selection Circuit 4402.

If 5 signal interface operation is selected, the “AUXI/O1 or TDI” signal4408 will operate as TDI 4112 of FIG. 41, the “TDI/TDO or TDO” signal4410 will operate as TDO signal 4114 of FIG. 41, the “AUXI/O2 or TMS”signal 4412 will operate as TMS signal 4116 of FIG. 41, and the “TMS/RCKor RCK” signal 4414 will operate as RCK signal 4118 of FIG. 41.

If 3 signal interface operation is selected, the “AUXI/O1 or TDI” signal4408 will operate as an auxiliary input or output signal, the “TDI/TDOor TDO” signal 4410 will operate as TDI/TDO signal 520 of FIG. 8, the“AUXI/O2 or TMS” signal 4412 will operate as an auxiliary input oroutput signal, and the “TMS/RCK or RCK” signal 4414 will operate asTMS/RCK signal 518 of FIG. 8.

When the instruction register 810 is reset, at power up or following ahard reset first protocol, it will output control 4416 to select eitherthe 3 or 5 signal interface to the Addressable Tap Domain Selectioncircuit 4402. Since the IEEE 1149.1 standard requires that its interfacebe enabled to operate following a reset or power up event, the 5 signalinterface is preferably the interface selected by the instructionregister 810 following reset or power up. However, while the 5 signalinterface is preferred for consistency to the IEEE 1149.1 standard,users of the present disclosure may select the 3 signal interface atreset/power up as well.

FIG. 45 illustrates an example of how the Interface Select Circuit 4404may be designed. The Interface Select Circuit includes I/O circuits 802and 804 of FIG. 8, TDO output buffer 4106 and TMS output buffer 4110 ofFIG. 41, multiplexers 4516-4526, I/O buffers 4528 and 4104, and I/Obuffers 4532 and 4108.

TDO 820 is coupled to an input of I/O circuit 802 and to the input ofbuffer 4106. “TDI/TDO or TDO” 4410 is coupled to an output of I/Ocircuit 802 and to the output of buffer 4106. TDI 824 is coupled, viamultiplexer 4516, to either an output of I/O circuit 802 or to theoutput of buffer 4104. “AUXI/O1 or TDI” 4408 is coupled to the input ofbuffer 4104 and to the output of buffer 4528. OE1 822 is coupled to thecontrol input of buffer 814 of I/O circuit 802 via multiplexer 4518 andto the control input of buffer 4106 via multiplexer 4520.

RCK 826 is coupled to an input of I/O circuit 804 and to the input ofbuffer 4110. “TMS/RCK or RCK” 4414 is coupled to an output of I/Ocircuit 804 and to the output of buffer 4110. TMS 830 is coupled, viamultiplexer 4522, to either an output of I/O circuit 804 or buffer 4108.“AUXI/O2 or TMS” 4412 is coupled to the input of buffer 4108 and to theoutput of buffer 4532. OE2 828 is coupled to the control input of buffer814 of I/O circuit 804 via multiplexer 4524 and to the control input ofbuffer 4110 via multiplexer 4526.

The output of buffer 4104 is coupled to an auxiliary input 1 (AUXIN1)signal 4504. The input of buffer 4528 is coupled to an auxiliary output1 (AUXOUT1) signal 4502. The output of buffer 4528 is coupled to“AUXI/O1 or TDI” 4408. The control input of buffer 4528 is coupled tocontrol signal 4512 from instruction control bus 4416.

The output of buffer 4532 is coupled to an auxiliary input 2 (AUXIN2)signal 4508. The input of buffer 4532 is coupled to an auxiliary output2 (AUXOUT2) signal 4506. The output of buffer 4532 is coupled to“AUXI/O2 or TMS” 4412. The control input of buffer 4532 is coupled tocontrol signal 4514 from instruction control bus 4416.

The select input of multiplexers 4516-4526 is coupled to control signal4510 from instruction control bus 4416. A low on control signal 4510enables the 3 signal interface mode of Interface Select Circuit 4404,and a high on control signal 4510 enables the 5 signal interface mode ofInterface Select Circuit 4404.

While control signal 4510 is high, multiplexer 4516 couples TDO 824 tothe output of buffer 4104, multiplexer 4518 couples OE1 822 to thecontrol input of buffer 4106, multiplexer 4520 couples a low (disable)signal to the control input of I/O circuit 802, multiplexer 4522 couplesTMS 830 to the output of buffer 4108, multiplexer 4524 couples OE2 828to the control input of buffer 4110, and multiplexer 4526 couples a low(disable) signal to the control input of I/O circuit 804. In this mode,the Interface Select Circuit 4404 enables the 5 signal interface tooperate the Addressable Tap Domain Selection Circuit 4402 as describedin FIG. 41. That is to say the “AUXI/O1 or TDI” 4408 signal operates asthe TDI signal 4112 of FIG. 41, the “TDI/TDO or TDO” 4410 signaloperates as the TDO 4114 signal of FIG. 41, the “AUXI/O2 or TMS” signal4412 operates as the TMS signal 4116 of FIG. 41, and the “TMS/RCK orRCK” 4414 signal operates as the RCK 4118 signal of FIG. 41.

While control signal 4510 is low, multiplexer 4516 couples TDO 824 tothe output of I/O circuit 802, multiplexer 4518 couples OE1 822 to thecontrol input of I/O circuit 802, multiplexer 4520 couples a low(disable) signal to the control input of buffer 4106, multiplexer 4522couples TMS 830 to the output of I/O circuit 804, multiplexer 4524couples OE2 828 to the control input of I/O circuit 804, and multiplexer4526 couples a low (disable) signal to the control input of buffer 4110.In this mode, the Interface Select Circuit 4404 enables the 3 signalinterface to operate the Addressable Tap Domain Selection Circuit 4402as described in FIG. 8. That is to say the “TDI/TDO or TDO” 4410 signaloperates as the TDI/TDO 520 signal of FIG. 8 and the “TMS/RCK or RCK”4414 signal operates as the TMS/RCK 518 signal of FIG. 8.

While control signal 4510 is low, selecting the 3 signal interface modeof operation, the “AUXI/O1 or TDI” signal 4408 can be used as an input,if control signal 4512 is set to disable buffer 4528, to transmit asignal to the AUXIN1 signal 4504 output. Alternately, if control signal4512 is set to enable buffer 4528, the “AUXI/O1 or TDI” signal 4408 canbe used as an output to transmit a signal from the AUXOUT1 signal 4502input.

While control signal 4510 is low, selecting the 3 signal interface modeof operation, the “AUXI/O2 or TMS” signal 4412 can be used as an input,if control signal 4514 is set to disable buffer 4532, to transmit asignal to the AUXIN2 signal 4508 output. Alternately, if control signal4514 is set to enable buffer 4532, the “AUXI/O2 or TMS” signal 4412 canbe used as an output to transmit a signal from the AUXOUT2 signal 4506input.

FIG. 46 illustrates an example of the configuration of the InterfaceSelect Circuit 4404 when it is in the 3 signal interface mode. In thismode, the Interface Select Circuit 4404 is configured to access theAddressable Tap Domain Selection Circuit 4402 using the 3 signals“TDI/TDO or TDO” 4410 (named simply TDI/TDO), “TMS/RCK or RCK” 4414(named simply TMS/RCK), and TCK 516 as described in FIG. 8. Since“AUXI/O1 or TDI” 4408 (named simply AUXI/O1) and “AUXI/O2 or TMS” 4412(named simply AUXI/O2) are not used as interface signals, they are shownbeing used for auxiliary input or output signals to AUXI/O bus 4406. Asseen in FIGS. 45 and 46, AUXI/O1 4408 can be programmed by instructioncontrol input 4512 of control bus 4416 to be an output for AUXOUT1 4502or an input for AUXIN1 4504. Likewise, AUXI/O2 4412 can be programmed byinstruction control input 4514 of control bus 4416 to be an output forAUXOUT2 4506 or an input for AUXIN2 4508. The AUXIN1 4504, AUXOUT1 4502,AUXIN2 4508, and AUXOUT2 4506 signals may be data signals, controlsignals, interrupt signals, triggering signals, or other types ofsignals that may be necessary to during test, debug, emulation, and/ortrace operations using the 3 signal interface.

FIG. 47 illustrates an example of the configuration of the InterfaceSelect Circuit 4404 when it is in the 5 signal interface mode. In thismode, the Interface Select Circuit 4404 is configured to access theAddressable Tap Domain Selection Circuit 4402 using the 5 signals“AUXI/O1 or TDI” 4408 (named simply TDI), “TDI/TDO or TDO” 4410 (namedsimply TDO), “AUXI/O2 or TMS” 4412 (named simply TMS), “TMS/RCK or RCK”4414 (named simply RCK), and TCK as described in FIG. 41. As seen, since“AUXI/O1 or TDI” 4408 (named simply TDI) and “AUXI/O2 or TMS” 4412(named simply TMS) are used as interface signals, they cannot be usedfor auxiliary I/O signals as they were in FIG. 45.

FIG. 48 illustrates a group of target devices 4204-4208 on a board orother substrate 4800, each target device including the Addressable TapDomain Selection Circuit 4402 of FIG. 44 and its selectable 3 or 5 pininterface, as well as Tap Domain Region 522. The selectable 3/5 pininterface of each target device is coupled to an external controller4808 via cable connector 4810 to provide access for test, debug,emulation, trace, and/or auxiliary I/O operations. Each target device4802-4806 may contain embedded core target circuits as described in FIG.17, which also are interfaced to the external controller 4808 via theselectable 3/5 pin interface. As indicated, the external controller 4808may be realized by using an interface card 4812 in a personal computer1726 to control the selectable 3/5 pin interface communication with thetargets 4802-4806 via a cable connection 4814. The interface card 4812is designed to communicate to the targets using either the 3 or 5 pininterface. The PC 1726 contains software for controlling the card 4812to access the targets using either the 3 and 5 pin interface, and toswitch the targets from operating in the 3 pin interface mode to the 5pin interface mode, and from operating in the 5 pin interface mode tothe 3 pin interface mode. The card 4814 is designed to interface withthe auxiliary I/O signals of target circuits when the 3 pin interfacemode is selected, and the PC 1726 contains software for comprehendingauxiliary I/O signaling from the targets.

Each target 4802-4806 has the previously mentioned local address toallow it to be individually addressed and instructed by the controller4808 using the second protocol in either the 3 or 5 pin interface modes.Following the individual addressing and instructing of a target usingthe second protocol, the Tap Domains 510 within the target may beaccessed by the controller 4808 using the third protocol in either the 3or 5 pin interface mode to perform test, debug, emulation, trace, and/orauxiliary I/O operations. Additionally, each target has the previouslymentioned global address to allow all targets to be simultaneouslyaddressed and instructed using the second protocol in either the 3 or 5pin interface mode for the purposes previously mentioned in regard toFIG. 17.

The controller 4808 may selectively switch the target circuits 4802-4806from operating in either the 3 or 5 pin interface mode by issuing aglobal address to all targets, then loading an instruction into alltargets that cause all targets to switch from their current interfacemode to the other interface mode. For example, if all targets areoperating in the 5 pin interface mode they can be switched to the 3 pininterface mode by the controller issuing a global address followed by aninstruction that selects the 3 pin interface mode of the targets.Likewise, if all targets are operating in the 3 pin interface mode theycan be switched to the 5 pin interface mode by the controller issuing aglobal address followed by an instruction that selects the 5 pininterface mode of the targets.

FIG. 49 illustrates the legacy target devices 1802-1806 of FIG. 18, eachincluding the standard IEEE 1149.1 TRST, TCK, TMS, TDI, and TDOterminals, and optionally the non-standard RCK terminal. The legacytarget devices could be ICs 1802-1806 on a board or other substrate4900, embedded core circuits 1802-1806 within an IC 4900, or embeddedcore circuits 1802-1806 within a core circuit 4900.

As seen, a separate device 4902 exists between the legacy target devices1802-1806 and the external controller 4808. This separate device 4902implements the Addressable Tap Domain Selection Circuit 4402 of FIG. 44and operates in either the 3 or 5 signal interface mode according thepreviously described first, second, and third protocols. It alsoincludes the previously described local and global addressing modes. Thelocal address is shown, in this example, as being input to the separatedevice 4902 on externally accessible terminals of device 4902. Theseparate device 4902 serves to provide the interface between thestandard IEEE 1149.1 (plus optional RCK) interface of each legacy targetdevice and the selectable 3 or 5 signal interface to the externalcontroller 4808. The operation of the separate device 4902 in accessingthe legacy device Tap Domains is the same as described in FIGS. 44-47where the Addressable Tap Domain Selection Circuit 4402 was describedaccessing the Tap Domains 510 of Tap Region 522.

The arrangement shown in FIG. 49 could represent the legacy targetdevices 1802-1806 and separate device 4902 as being; (1) ICs/die on aboard or substrate 4900, embedded core circuits within an IC 4900, or(3) embedded core circuits within a core circuit 4900. FIG. 49advantageously illustrates how legacy devices designed using theconventional IEEE 1149.1 interface and optional RCK can be interfaced tothe selectable 3 or 5 signal interface controller 4808 by providing theAddressable Tap Selection Circuit 4402 as a separate circuit to serve asthe interface between the legacy devices 1802-1806 and externalcontroller 4808. As described for separate circuits 1808 and 4302 ofFIGS. 18 and 432, the separate circuit 4902 could contain only theAddressable Tap Domain Selection Circuit 4402 or it could contain theAddressable Tap Domain Selection Circuit 4402 along with other circuits.

As seen in FIG. 49, the Addressable Tap Selection Circuit 4402 ofseparate circuit 4902 has terminals for connecting to auxiliary I/Osignals 4502-4508. Thus when separate circuit 4902 is set to operate inthe 3 signal interface mode, the “AUXI/O1 or TDI” signal 4408 and the“AUXI/O2 or TMS” signal 4412 can be used for communicating auxiliary I/Osignals between a further circuit on assembly 4900 and the controller4808. The further circuit could be one or more of the target circuits1802-1806, or a circuit separate from target circuits 1802-1806. Thefurther circuit could also be a circuit contained within separatecircuit 4902.

Although the present disclosure has been described in detail, it shouldbe understood that various changes, substitutions and alterations may bemade without departing from the spirit and scope of the disclosure asdefined by the appended claims.

1. An integrated circuit comprising: A. plural TAP domains, each domainhaving a TDI input terminal, a TDO output terminal, a TCK inputterminal, a TMS input terminal, and a RCK output terminal; and B. a TAPdomain selection circuit, the selection circuit having a separate set ofoutputs and at least one input for each TAP domain, each set including aTDI output connected to a TDI input terminal, a TDO input connected to aTDO output terminal, a TCK output connected to a TCK input terminal, aTMS output connected to a TMS input terminal, and a RCK input connectedto a RCK output terminal, the selection circuit including an interfaceselect circuit including: i. an instruction control bus input; ii. a TMSoutput lead coupled to the TDI input of each set; iii. an AUX I/O 2 orTMS lead; iv. a TMS/RCK or RCK lead; v. a first buffer having an inputconnected to the AUX I/O 2 or TMS lead and an output; vi. an I/O circuithaving an input connected to the TMS/RCK or RCK lead and an output; andvii. a multiplexer having an input connected to the output of the firstbuffer, another input connected to the output of the I/O circuit, acontrol input connected to the instruction control bus input, and anoutput connected to the TMS output lead.